Bug 2015793: Run OLM's collect profiles job on the management cluster#583
Conversation
|
Skipping CI for Draft Pull Request. |
|
@awgreene: This pull request references Bugzilla bug 2015793, which is invalid:
Comment DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
Blocked until openshift/operator-framework-olm#208 is merged into 4.9 |
4b7450e to
8fd08bc
Compare
|
/bugzilla refresh |
|
@awgreene: This pull request references Bugzilla bug 2015793, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
Requesting review from QA contact: DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/hold until openshift/operator-framework-olm#208 merges |
8fd08bc to
80f5b8c
Compare
| - name: profile-collector | ||
| secret: | ||
| secretName: olm-profile-collector | ||
| secretName: pprof-cert |
80f5b8c to
a909db1
Compare
|
/retest |
| // Collect Profiles | ||
| collectProfilesConfigMap := manifests.CollectProfilesConfigMap(hcp.Namespace) | ||
| olm.ReconcileCollectProfilesConfigMap(collectProfilesConfigMap, p.OwnerRef, p.OLMImage, hcp.Namespace) | ||
| if err := r.Create(ctx, collectProfilesConfigMap); err != nil && !apierrors.IsAlreadyExists(err) { |
There was a problem hiding this comment.
Helpful note: The pprof config shouldn't be modified - it allows users to disable the cronjob and the generated configmaps.
There was a problem hiding this comment.
I think we need to decide which user can modify the configmap. If it's the owner of the guest cluster (aka customer), then we should probably create this in the guest cluster and mirror its content back to the control plane. If it's meant to be configured by the cluster provider (aka management), then there likely should be a way to modify it via the HostedCluster API. I wouldn't expect anyone to make changes directly to configmaps in the control plane's namespace.
There was a problem hiding this comment.
I believe the owner of the control plane should be responsible for modifying this configMap. It acts as an emergency escape hatch for disabling the cronjob, which runs on the management cluster.
If we want to configure this via the hostedCluster API, we can:
- Modify the hosted control plane operator to create/update this configMap.
- Introduce a knob on the hostedCluster API to set the value in the configMap.
| } | ||
|
|
||
| collectProfilesSecret := manifests.CollectProfilesSecret(hcp.Namespace) | ||
| olm.ReconcileCollectProfilesSecret(collectProfilesSecret, p.OwnerRef, p.OLMImage, hcp.Namespace) |
There was a problem hiding this comment.
Helpful note: The pprof secret shouldn't be modified - it allows the cronjob to frequently change the pprof secret.
|
I test this PR, but failed to create the hosted cluster, details: https://bugzilla.redhat.com/show_bug.cgi?id=2015793#c1 |
|
/retest |
1 similar comment
|
/retest |
a909db1 to
b108e6c
Compare
Problem: In 4.9, OLM introduce a job that collects the data from the pprof endpoint ever 15 minutes. This job currently runs on the guest cluster but should run on the control plane. Solution: Run the profile collection job on the control plane.
b108e6c to
43de60d
Compare
|
openshift/operator-framework-olm#208 has merged |
|
/lgtm |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: awgreene, csrwng The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@awgreene: All pull requests linked via external trackers have merged: Bugzilla bug 2015793 has been moved to the MODIFIED state. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
No description provided.