-
Notifications
You must be signed in to change notification settings - Fork 66
⚠️ OPRUN-4075: Move to a helm-based configuration #2145
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,5 @@ | ||
module _ // Auto generated by https://github.com/bwplotka/bingo. DO NOT EDIT | ||
|
||
go 1.24.3 | ||
|
||
require helm.sh/helm/v3 v3.18.4 // cmd/helm |
Large diffs are not rendered by default.
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -24,7 +24,7 @@ To enable the Helm Chart support feature gate, you need to patch the `operator-c | |
2. **Wait for the controller manager pods to be ready:** | ||
|
||
```bash | ||
$ kubectl -n olmv1-system wait --for condition=ready pods -l control-plane=operator-controller-controller-manager | ||
$ kubectl -n olmv1-system wait --for condition=ready pods -l apps.kubernetes.io/name=operator-controller | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think you added it in the RFC, but could it not be a breaking change? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I don't think it's a breaking change, it's only in our draft documentation. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I mean, people could teorically have scripts and etc to filter things with There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. theoretically... but I think our user base is very small and OCP focused. Also, I don't think we consider our YAML a published API. |
||
``` | ||
|
||
Once the above wait condition is met, the `HelmChartSupport` feature gate should be enabled in operator controller. | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,8 @@ | ||
# Default values for OLMv1. | ||
# This is a YAML-formatted file. | ||
# Declare variables to be passed into your templates. | ||
|
||
# List of components to include | ||
options: | ||
certManager: | ||
enabled: true |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,8 @@ | ||
# e2e values for OLMv1. | ||
# This is a YAML-formatted file. | ||
# Declare variables to be passed into your templates. | ||
|
||
# List of components to include | ||
options: | ||
e2e: | ||
enabled: true |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
# experimental values for OLMv1. | ||
# This is a YAML-formatted file. | ||
# Declare variables to be passed into your templates. | ||
|
||
# List of enabled experimental features for operator-controller | ||
# Use with {{- if has "FeatureGate" .Value.operatorControllerFeatures }} | ||
# to pull in resources or additions | ||
operatorControllerFeatures: | ||
- WebhookProviderCertManager | ||
- SingleOwnNamespaceInstallSupport | ||
- PreflightPermissions | ||
- HelmChartSupport | ||
|
||
# List of enabled experimental features for catalogd | ||
# Use with {{- if has "FeatureGate" .Value.catalogdFeatures }} | ||
# to pull in resources or additions | ||
catalogdFeatures: | ||
- APIV1MetasHandler | ||
|
||
# This can be one of: standard or experimental | ||
options: | ||
featureSet: experimental |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
# Patterns to ignore when building packages. | ||
# This supports shell glob matching, relative path matching, and | ||
# negation (prefixed with !). Only one pattern per line. | ||
.DS_Store | ||
# Common VCS dirs | ||
.git/ | ||
.gitignore | ||
.bzr/ | ||
.bzrignore | ||
.hg/ | ||
.hgignore | ||
.svn/ | ||
# Common backup files | ||
*.swp | ||
*.bak | ||
*.tmp | ||
*.orig | ||
*~ | ||
# Various IDEs | ||
.project | ||
.idea/ | ||
*.tmproj | ||
.vscode/ |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
apiVersion: v2 | ||
name: olmv1 | ||
description: A Helm chart for OLMv1 | ||
|
||
# A chart can be either an 'application' or a 'library' chart. | ||
# | ||
# Application charts are a collection of templates that can be packaged into versioned archives | ||
# to be deployed. | ||
# | ||
# Library charts provide useful utilities or functions for the chart developer. They're included as | ||
# a dependency of application charts to inject those utilities and functions into the rendering | ||
# pipeline. Library charts do not define any templates and therefore cannot be deployed. | ||
type: application | ||
|
||
# This is the chart version. This version number should be incremented each time you make changes | ||
# to the chart and its templates, including the app version. | ||
# Versions are expected to follow Semantic Versioning (https://semver.org/) | ||
version: 0.1.0 |
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Helm charts usually follow a clear folder structure under /templates to group related files.
Putting everything in one place makes it harder to read, review, and maintain.
So, wdyt? Let’s split these into logical subfolders so it’s easier to find and manage resources.
Following a proposed structure would like
Then, the values could be something like
In the templates we would need add helpers like
Maybe the calls could be something like:
disclaimer:
Assisted-by: AI to help build the examples to ilustrate the suggestion
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You know, I tried to put files into individual directories, and it wasn't working. I will try again.
experimental
has to be a global option, so I think I will be keeping that as is; I want to keep the inputs simple, and not have to manage multipleexperimental
flags.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Although, I like the idea of being able to add sets...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So, now there is the capability to do
--set
via environment variable.