-
Notifications
You must be signed in to change notification settings - Fork 8
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
Explore ytt based conventions #58
Labels
enhancement
New feature or request
Comments
This would be amazing. I can think of a bunch of use cases this would solve for me and would be much easier to implement custom conventions |
Yes please! Being able to quickly implement template-based conventions with ytt is going to be extremely accessible to end users, and allow ops teams to realize enormous value from supply chains. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The current approach to defining an opinion source is via a webhook to a remote process. While flexible, this approach introduces networks and misconfigurations that can affect system stability. We should also explore ytt as a mechanism to run arbitrary code safely within the controller process.
Open questions:
Proposed approach:
The
.spec.webhook
section would remain, but be mutually exclusive with.spec.ytt
.The structure being templated is the PodTemplateSpec, with image metadata exposed as a ytt value.
The text was updated successfully, but these errors were encountered: