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

Provide information concerning HashiCorp Vault in CRD #1826

Closed
tomkerkhove opened this issue May 25, 2021 · 8 comments · Fixed by #1862
Closed

Provide information concerning HashiCorp Vault in CRD #1826

tomkerkhove opened this issue May 25, 2021 · 8 comments · Fixed by #1862
Labels
feature-request All issues for new features that have not been committed to needs-discussion

Comments

@tomkerkhove
Copy link
Member

Proposal

Provide information concerning HashiCorp Vault in CRD since it's not surfaced yet when doing k get triggerauthentication.

Use-Case

No response

Anything else?

This would be more consistent since other stores are shown.

@Shubham82
Copy link
Contributor

Hi @tomkerkhove
Just for confirmation in this, you want that when we run k get triggerauthentication then it would show HashiCorp Vault information also. if yes then in HashiCorp Vault there are the following fields:

address
authentication
role
mount
credential
   token
   serviceAccount

which fields you want to show them in the kubectl get ta command.

@tomkerkhove
Copy link
Member Author

I'd keep it simple for now and just show the address, what do you think?

@Shubham82
Copy link
Contributor

yha, I am also thinking of the address field as it is more suited than other fields.

@Shubham82
Copy link
Contributor

Shubham82 commented Jun 3, 2021

Hi @tomkerkhove @zroubalik

Please suggest the name from the following for the HashiCorp Vault field which shows on running kubectl get ta

1) HashiCorpVault-ADDRESS
2) HashiCorpVault-Address
3) HashiCorp-Address
4) HashiCorp-ADDRESS
5) HASHICORP-ADDRESS

Any other name you want to add other than this.

@zroubalik
Copy link
Member

HCVaultAddress or VaultAddress or? I keep it on @tomkerkhove and his preference.

@tomkerkhove
Copy link
Member Author

Let's go with VaultAddress

@Shubham82
Copy link
Contributor

Thanks, @tomkerkhove @zroubalik
VaultAddress seems good.

@Shubham82
Copy link
Contributor

fixed for both ta and cta here #1862

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request All issues for new features that have not been committed to needs-discussion
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants