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

Support resource templating via operator plugin #524

Open
Danil-Grigorev opened this issue May 9, 2024 · 1 comment
Open

Support resource templating via operator plugin #524

Danil-Grigorev opened this issue May 9, 2024 · 1 comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@Danil-Grigorev
Copy link
Member

User Story

As a user I would like to template and apply my infrastructure manifests via operator plugin and reuse existing operator state for templating, so I don’t have to duplicate secrets location.

Detailed Description

Currently clusterctl is used to template cluster definitions by using local environment and clusterctl.yaml config. Clusterctl does not rely on cluster-api installation to provide data for templated definitions. Operator, on the other hand, is using secrets to enable a provider and prepare environment for it, therefore removing reliance on the local machine environment.

Operator plugin may leverage this state to template infrastructure definitions on submission.

Anything else you would like to add:

/kind feature

@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 9, 2024
@Fedosin
Copy link
Contributor

Fedosin commented May 9, 2024

/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

3 participants