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

GitOps Catalog should be able to detokenize cluster name #2070

Closed
1 of 2 tasks
fharper opened this issue Jan 29, 2024 · 1 comment
Closed
1 of 2 tasks

GitOps Catalog should be able to detokenize cluster name #2070

fharper opened this issue Jan 29, 2024 · 1 comment
Assignees
Labels
feature Something new

Comments

@fharper
Copy link
Contributor

fharper commented Jan 29, 2024

What is your feature idea?

The GitOps Catalog entry should be able to add something like <CLUSTER_NAME> and the installation of that new application should be able to detokenize it so the application has the proper name.

Why is it needed?

It is needed for some applications, like the Kubescape Operator at https://github.com/kubefirst/gitops-catalog/blob/main/kubescape-operator/application.yaml#L17 .

Right now, the user needs to to click install, and manually update the YAML file in their gitops repository.

Is this missing feature preventing you from using kubefirst?

  • Yes

Code of Conduct

  • I agree to follow this project's Code of Conduct
@fharper fharper added the feature Something new label Jan 29, 2024
@fharper
Copy link
Contributor Author

fharper commented Feb 2, 2024

@fharper fharper closed this as completed Feb 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Something new
Projects
None yet
Development

No branches or pull requests

2 participants