https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
c
there are not.
c
https://raw.githubusercontent.com/jetstack/cert-manager/v0.7.2/deploy/manifests/cert-manager.yaml has a 
ServiceAccount
called 
cert-manager-cainjector
, but it is skipped over.
The ONLY thing I can see that MAY cause it, is the fact that it is preceded by:
Copy code
---
---
Copy code
---
---
# Source: cert-manager/charts/cainjector/templates/serviceaccount.yaml
apiVersion: v1
kind: ServiceAccount
metadata:
  name: cert-manager-cainjector
  namespace: "cert-manager"
  labels:
    app: cainjector
    chart: cainjector-v0.7.2
    release: cert-manager
    heritage: Tiller
c
that should be ok
is anything else skipped?
c
Nope
It’s the only resource in the entire file that is missing.
c
do you have a reliable reproduction?
c
Haven’t tried to reproduce it in a separate project at all.
Copy code
new k8s.yaml.ConfigFile('cert-manager', {
  file: '<https://raw.githubusercontent.com/jetstack/cert-manager/v0.7.2/deploy/manifests/cert-manager.yaml>',
  transformations: [
    (resource: any) => {
      if (resource.kind == 'Deployment' && resource.metadata.name == 'cert-manager') {
        resource.spec.template.spec.containers[0].args.push(
          ...[
            '--default-issuer-name=letsencrypt',
            '--default-issuer-kind=ClusterIssuer',
            '--default-acme-issuer-challenge-type=dns01',
            '--default-acme-issuer-dns01-provider-name=route53'
          ]
        );

        resource.spec.template.spec.containers[0].env.push([
          {
            name: 'AWS_REGION',
            value: awsConfig.require('region')
          },
          {
            name: 'AWS_ACCESS_KEY_ID',
            value: awsAccessKey.id
          },
          {
            name: 'AWS_SECRET_ACCESS_KEY',
            value: awsAccessKey.secret
          }
        ]);
      }
    }
  ]
});
c
alright, can you file a bug so we don’t forget?
c
Yes I can.
c
thanks!
c
Oddly, after doing a destroy and trying again, it showed up.
Open in Slack
PreviousNext
Powered by

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Powered by