Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Empty Target field in kubectl get bundle #343

Closed
qds-x opened this issue May 1, 2024 · 3 comments · Fixed by #344
Closed

Empty Target field in kubectl get bundle #343

qds-x opened this issue May 1, 2024 · 3 comments · Fixed by #344

Comments

@qds-x
Copy link

qds-x commented May 1, 2024

After having upgraded to 0.9.2 from 0.5.0 we see the 'Target' field empty in the following output

➜  k get bundle
NAME                   TARGET   SYNCED   REASON   AGE
test-bundle-injected            True     Synced   4m27s

Everything functions as expected.

Tested this on a fresh minikube instance and got the same thing. I used a very simple bundle defn:

apiVersion: trust.cert-manager.io/v1alpha1
kind: Bundle
metadata:
  name: "test-bundle-injected" 
spec:
  sources:
  - inLine: |
      -----BEGIN CERTIFICATE-----
      ...
      -----END CERTIFICATE-----
  target:
    configMap:
      key: cert.pem

Happy to provide more information if required.

@qds-x
Copy link
Author

qds-x commented May 1, 2024

I'm pretty sure this is because the field is taken from status.target.configMap.key which doesn't exist

@erikgb
Copy link
Contributor

erikgb commented May 1, 2024

Thanks for reporting this! I submitted the PR to remove target from status. 😊 Will take a look!

@qds-x
Copy link
Author

qds-x commented May 1, 2024

Thanks for reporting this! I submitted the PR to remove target from status. 😊 Will take a look!

No problemo. Obviously it doesn't really affect anything but it made us think for a second that something was off with our bundle defns. Thanks for looking at it so quickly!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants