-
Notifications
You must be signed in to change notification settings - Fork 77
CNF-22194 Core: ensure one copy of MachineConfigs in Core RDS #825
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 3 commits
7c2e3d1
57c42ae
915932c
468c267
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 |
|---|---|---|
|
|
@@ -91,7 +91,6 @@ parts: | |
| - name: optional-networking | ||
| anyOf: | ||
| - path: optional/networking/networkAttachmentDefinition.yaml | ||
| - path: optional/networking/multus/tap_cni/mc_rootless_pods_selinux.yaml | ||
| - path: required/networking/metallb/community.yaml | ||
| - path: optional/networking/nodeNetworkConfigurationPolicy.yaml | ||
| - name: networking-firewall | ||
|
|
@@ -159,17 +158,17 @@ parts: | |
| - name: other | ||
| description: |- | ||
| https://docs.redhat.com/en/documentation/openshift_container_platform/4.22/html/scalability_and_performance/telco-core-ref-design-specs#node-configuration-crs | ||
|
|
||
| Reference MachineConfig CRs are validated from telco-core/install/extra-manifests | ||
| via compare.sh --check-extra-manifests, not from reference-crs. | ||
|
Comment on lines
+162
to
+163
Collaborator
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. At runtime I don't think this works. compare.sh would verify the repository contents, but kube-compare needs to include all the lines which are deleted in order to verify that these CRs exist and are correct on a deployed cluster.
Contributor
Author
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. Hi @imiller0, i understand your concern about removing the MachineConfig CRs from metadata.yaml. |
||
| components: | ||
| - name: other | ||
| anyOf: | ||
| - path: optional/other/control-plane-load-kernel-modules.yaml | ||
| - path: optional/other/monitoring-config-cm.yaml | ||
| config: | ||
| perField: | ||
| - pathToKey: data."config.yaml" | ||
| inlineDiffFunc: capturegroups | ||
| - path: optional/other/worker-load-kernel-modules.yaml | ||
| - path: optional/other/sctp_module_mc.yaml | ||
| - name: precache | ||
| anyOf: | ||
| - path: optional/other/precache/controlplane-olm-pinned-images.yaml | ||
|
|
@@ -198,14 +197,6 @@ parts: | |
| - name: other | ||
| anyOf: | ||
| - path: optional/tuning/control-plane-system-reserved.yaml | ||
| - name: kdump-configuration | ||
| allOf: | ||
| - path: optional/other/kdump-master.yaml | ||
| - path: optional/other/kdump-worker.yaml | ||
| - name: mount-namespace-configuration | ||
| allOf: | ||
| - path: optional/other/mount_namespace_config_master.yaml | ||
| - path: optional/other/mount_namespace_config_worker.yaml | ||
| - name: optional-cert-manager | ||
| description: |- | ||
| Cert-manager operator for automated certificate management | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,5 +1,6 @@ | ||
| # optional | ||
| # count: 1 | ||
| --- | ||
| apiVersion: machineconfiguration.openshift.io/v1 | ||
| kind: MachineConfig | ||
| metadata: | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,5 +1,6 @@ | ||
| # optional | ||
| # count: 1 | ||
| --- | ||
| apiVersion: machineconfiguration.openshift.io/v1 | ||
| kind: MachineConfig | ||
| metadata: | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,10 +1,15 @@ | ||
| # Custom CRs | ||
| This directory is a placeholder for additional custom CRs which are | ||
| outside the scope of the reference CRs. | ||
|
|
||
| ## Reference MCPs | ||
| The MCP CRs contained here are examples for a multi-mcp cluster and | ||
| are used to build policies which accelerate initial rollout of | ||
| configuration by increasing maxUnavailable and manipulating the MCP | ||
| pause. The MCPs should be created during initial cluster installation | ||
| in a paused state with maxUnavailable of 100%. | ||
|
|
||
|
Contributor
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. IMHO this part is still relevant: |
||
| This directory holds CRs referenced by PolicyGenerator manifests under | ||
| `telco-core/configuration/`. Paths must stay under that directory tree because | ||
| the PolicyGenerator kustomize plugin rejects manifest paths outside it (no `../`). | ||
|
|
||
| ## MachineConfigPool examples | ||
|
|
||
| Reference `MachineConfigPool` CRs (`mcp-worker-1.yaml` through `mcp-worker-3.yaml`) | ||
| are duplicated here for day-N policies (`core-finish`, `core-upgrade`, | ||
| `core-upgrade-finish`). The canonical install-time copies live under | ||
| `telco-core/install/extra-manifests/` and must remain identical; `compare.sh | ||
| --check-extra-manifests` enforces that. | ||
|
|
||
| Other custom content (for example `subscription-validator.yaml`) also belongs here. | ||
This file was deleted.
This file was deleted.
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 it's now mandatory to have/use RDS HUB cluster?