🐛 Removing Unused and Insecure Manifests for Prometheus since its integration is not supported #1535
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… integration is not supported
We are not using these manifests or supporting this option. Therefore, they should be removed, as they are not configured to use certificates and have insecureSkipVerify: false, which promotes an insecure setup by default.
If we want enable this option then we need configure it with:
```yaml
apiVersion: monitoring.coreos.com/v1
kind: ServiceMonitor
metadata:
labels:
control-plane: operator-controller-controller-manager
name: controller-manager-metrics-monitor
namespace: system
spec:
endpoints:
- path: /metrics
port: https
scheme: https
bearerTokenFile: /var/run/secrets/kubernetes.io/serviceaccount/token
tlsConfig:
insecureSkipVerify: false
ca:
secret:
name: olmv1-cert
key: ca.crt
cert:
secret:
name: olmv1-cert
key: tls.cert
keySecret:
name: olmv1-cert
key: tls.key
selector:
matchLabels:
control-plane: operator-controller-controller-manager
```
camilamacedo86
changed the title
✅ Deploy Preview for olmv1 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1535 +/- ##
=======================================
Coverage 74.25% 74.25%
=======================================
Files 42 42
Lines 3329 3329
=======================================
Hits 2472 2472
Misses 676 676
Partials 181 181
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
camilamacedo86
changed the title
joelanford
approved these changes
Jan 3, 2025
Merged
via the queue into
operator-framework:main
with commit Jan 3, 2025
de6a813
30 of 32 checks passed
camilamacedo86
added a commit
to camilamacedo86/operator-controller
that referenced
this pull request
Jan 5, 2025
… integration is not supported (operator-framework#1535) We are not using these manifests or supporting this option. Therefore, they should be removed, as they are not configured to use certificates and have insecureSkipVerify: false, which promotes an insecure setup by default. If we want enable this option then we need configure it with: ```yaml apiVersion: monitoring.coreos.com/v1 kind: ServiceMonitor metadata: labels: control-plane: operator-controller-controller-manager name: controller-manager-metrics-monitor namespace: system spec: endpoints: - path: /metrics port: https scheme: https bearerTokenFile: /var/run/secrets/kubernetes.io/serviceaccount/token tlsConfig: insecureSkipVerify: false ca: secret: name: olmv1-cert key: ca.crt cert: secret: name: olmv1-cert key: tls.cert keySecret: name: olmv1-cert key: tls.key selector: matchLabels: control-plane: operator-controller-controller-manager ```
camilamacedo86
added a commit
to camilamacedo86/operator-controller
that referenced
this pull request
Jan 6, 2025
… integration is not supported (operator-framework#1535) We are not using these manifests or supporting this option. Therefore, they should be removed, as they are not configured to use certificates and have insecureSkipVerify: false, which promotes an insecure setup by default. If we want enable this option then we need configure it with: ```yaml apiVersion: monitoring.coreos.com/v1 kind: ServiceMonitor metadata: labels: control-plane: operator-controller-controller-manager name: controller-manager-metrics-monitor namespace: system spec: endpoints: - path: /metrics port: https scheme: https bearerTokenFile: /var/run/secrets/kubernetes.io/serviceaccount/token tlsConfig: insecureSkipVerify: false ca: secret: name: olmv1-cert key: ca.crt cert: secret: name: olmv1-cert key: tls.cert keySecret: name: olmv1-cert key: tls.key selector: matchLabels: control-plane: operator-controller-controller-manager ```
camilamacedo86
added a commit
to camilamacedo86/operator-controller
that referenced
this pull request
Jan 6, 2025
… integration is not supported (operator-framework#1535) We are not using these manifests or supporting this option. Therefore, they should be removed, as they are not configured to use certificates and have insecureSkipVerify: false, which promotes an insecure setup by default. If we want enable this option then we need configure it with: ```yaml apiVersion: monitoring.coreos.com/v1 kind: ServiceMonitor metadata: labels: control-plane: operator-controller-controller-manager name: controller-manager-metrics-monitor namespace: system spec: endpoints: - path: /metrics port: https scheme: https bearerTokenFile: /var/run/secrets/kubernetes.io/serviceaccount/token tlsConfig: insecureSkipVerify: false ca: secret: name: olmv1-cert key: ca.crt cert: secret: name: olmv1-cert key: tls.cert keySecret: name: olmv1-cert key: tls.key selector: matchLabels: control-plane: operator-controller-controller-manager ```
camilamacedo86
added a commit
to camilamacedo86/operator-controller
that referenced
this pull request
Jan 6, 2025
… integration is not supported (operator-framework#1535) We are not using these manifests or supporting this option. Therefore, they should be removed, as they are not configured to use certificates and have insecureSkipVerify: false, which promotes an insecure setup by default. If we want enable this option then we need configure it with: ```yaml apiVersion: monitoring.coreos.com/v1 kind: ServiceMonitor metadata: labels: control-plane: operator-controller-controller-manager name: controller-manager-metrics-monitor namespace: system spec: endpoints: - path: /metrics port: https scheme: https bearerTokenFile: /var/run/secrets/kubernetes.io/serviceaccount/token tlsConfig: insecureSkipVerify: false ca: secret: name: olmv1-cert key: ca.crt cert: secret: name: olmv1-cert key: tls.cert keySecret: name: olmv1-cert key: tls.key selector: matchLabels: control-plane: operator-controller-controller-manager ```
camilamacedo86
added a commit
to camilamacedo86/operator-controller
that referenced
this pull request
Jan 6, 2025
… integration is not supported (operator-framework#1535) We are not using these manifests or supporting this option. Therefore, they should be removed, as they are not configured to use certificates and have insecureSkipVerify: false, which promotes an insecure setup by default. If we want enable this option then we need configure it with: ```yaml apiVersion: monitoring.coreos.com/v1 kind: ServiceMonitor metadata: labels: control-plane: operator-controller-controller-manager name: controller-manager-metrics-monitor namespace: system spec: endpoints: - path: /metrics port: https scheme: https bearerTokenFile: /var/run/secrets/kubernetes.io/serviceaccount/token tlsConfig: insecureSkipVerify: false ca: secret: name: olmv1-cert key: ca.crt cert: secret: name: olmv1-cert key: tls.cert keySecret: name: olmv1-cert key: tls.key selector: matchLabels: control-plane: operator-controller-controller-manager ```
camilamacedo86
added a commit
to camilamacedo86/operator-controller
that referenced
this pull request
Jan 6, 2025
… integration is not supported (operator-framework#1535) We are not using these manifests or supporting this option. Therefore, they should be removed, as they are not configured to use certificates and have insecureSkipVerify: false, which promotes an insecure setup by default. If we want enable this option then we need configure it with: ```yaml apiVersion: monitoring.coreos.com/v1 kind: ServiceMonitor metadata: labels: control-plane: operator-controller-controller-manager name: controller-manager-metrics-monitor namespace: system spec: endpoints: - path: /metrics port: https scheme: https bearerTokenFile: /var/run/secrets/kubernetes.io/serviceaccount/token tlsConfig: insecureSkipVerify: false ca: secret: name: olmv1-cert key: ca.crt cert: secret: name: olmv1-cert key: tls.cert keySecret: name: olmv1-cert key: tls.key selector: matchLabels: control-plane: operator-controller-controller-manager ```
camilamacedo86
added a commit
to camilamacedo86/operator-controller
that referenced
this pull request
Jan 6, 2025
… integration is not supported (operator-framework#1535) We are not using these manifests or supporting this option. Therefore, they should be removed, as they are not configured to use certificates and have insecureSkipVerify: false, which promotes an insecure setup by default. If we want enable this option then we need configure it with: ```yaml apiVersion: monitoring.coreos.com/v1 kind: ServiceMonitor metadata: labels: control-plane: operator-controller-controller-manager name: controller-manager-metrics-monitor namespace: system spec: endpoints: - path: /metrics port: https scheme: https bearerTokenFile: /var/run/secrets/kubernetes.io/serviceaccount/token tlsConfig: insecureSkipVerify: false ca: secret: name: olmv1-cert key: ca.crt cert: secret: name: olmv1-cert key: tls.cert keySecret: name: olmv1-cert key: tls.key selector: matchLabels: control-plane: operator-controller-controller-manager ```
camilamacedo86
added a commit
to camilamacedo86/operator-controller
that referenced
this pull request
Jan 8, 2025
… integration is not supported (operator-framework#1535) We are not using these manifests or supporting this option. Therefore, they should be removed, as they are not configured to use certificates and have insecureSkipVerify: false, which promotes an insecure setup by default. If we want enable this option then we need configure it with: ```yaml apiVersion: monitoring.coreos.com/v1 kind: ServiceMonitor metadata: labels: control-plane: operator-controller-controller-manager name: controller-manager-metrics-monitor namespace: system spec: endpoints: - path: /metrics port: https scheme: https bearerTokenFile: /var/run/secrets/kubernetes.io/serviceaccount/token tlsConfig: insecureSkipVerify: false ca: secret: name: olmv1-cert key: ca.crt cert: secret: name: olmv1-cert key: tls.cert keySecret: name: olmv1-cert key: tls.key selector: matchLabels: control-plane: operator-controller-controller-manager ```
camilamacedo86
added a commit
to camilamacedo86/operator-controller
that referenced
this pull request
Jan 8, 2025
… integration is not supported (operator-framework#1535) We are not using these manifests or supporting this option. Therefore, they should be removed, as they are not configured to use certificates and have insecureSkipVerify: false, which promotes an insecure setup by default. If we want enable this option then we need configure it with: ```yaml apiVersion: monitoring.coreos.com/v1 kind: ServiceMonitor metadata: labels: control-plane: operator-controller-controller-manager name: controller-manager-metrics-monitor namespace: system spec: endpoints: - path: /metrics port: https scheme: https bearerTokenFile: /var/run/secrets/kubernetes.io/serviceaccount/token tlsConfig: insecureSkipVerify: false ca: secret: name: olmv1-cert key: ca.crt cert: secret: name: olmv1-cert key: tls.cert keySecret: name: olmv1-cert key: tls.key selector: matchLabels: control-plane: operator-controller-controller-manager ```
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We are not using these manifests or supporting this option. Therefore, they should be removed. They are not configured to use certificates and have insecureSkipVerify: false, which promotes an insecure setup by default.
As we discussed in the Community Meeting we agreed in remove those