search

rifaterdemsahin / prometheusremotewrite

Prometheus Remote Write On MiniKube
0 stars 0 forks source link

Missing Pods Instsance #1

Open rifaterdemsahin opened 1 day ago

rifaterdemsahin commented 1 day ago

Instance Pods Are missing image

PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code> minikube start

PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code> � kubectl set-context minikube

Oops, something went wrong. Please report this bug with the details below. Report on GitHub: https://github.com/PowerShell/PSReadLine/issues/new

Environment

PSReadLine: 2.0.0 PowerShell: 5.1.22621.4249 OS: Microsoft Windows 10.0.22631 Last 200 Keys

 Backspace Backspace Backspace Backspace Backspace Backspace Backspace Backspace m k d i r Spacebar o r Backspace Backspace p r o Tab LeftArrow RightArrow Backspace 1 Backspace 2 Enter
 c d Spacebar p r o Tab Tab Enter
 g i t Spacebar g Backspace c l o n e Spacebar g i t @ g i t h u b . c o m : r i f a t e r d e m s a h i n / p r o m e t h e u s r e m o t e w r i t e . g i t Enter LeftWindows c d Spacebar C o d e Enter
 l s Enter
 c d Spacebar p r o Tab Enter
 c d Spacebar c o d e Enter
 l s Enter
 m i n i k u b e Spacebar s t a r t Enter
 m i n i k u b e Spacebar s t a t u s Enter
 � Spacebar k u b e c t l Spacebar s e t - c o n t e x t Spacebar m i n i k u b e Enter

Exception

System.Text.EncoderFallbackException: Unable to translate Unicode character \uD83D at index 0 to specified code page.
   at System.Text.EncoderExceptionFallbackBuffer.Fallback(Char charUnknown, Int32 index)
   at System.Text.EncoderFallbackBuffer.InternalFallback(Char ch, Char*& chars)
   at System.Text.UTF8Encoding.GetBytes(Char* chars, Int32 charCount, Byte* bytes, Int32 byteCount, EncoderNLS baseEncoder)
   at System.Text.EncoderNLS.GetBytes(Char[] chars, Int32 charIndex, Int32 charCount, Byte[] bytes, Int32 byteIndex, Boolean flush)
   at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
   at System.IO.StreamWriter.Dispose(Boolean disposing)
   at System.IO.TextWriter.Dispose()
   at Microsoft.PowerShell.PSConsoleReadLine.<>c__DisplayClass83_0.<WriteHistoryRange>b__0()
   at Microsoft.PowerShell.PSConsoleReadLine.WithHistoryFileMutexDo(Int32 timeout, Action action)
   at Microsoft.PowerShell.PSConsoleReadLine.MaybeAddToHistory(String result, List`1 edits, Int32 undoEditIndex, Boolean fromDifferentSession, Boolean fromInitialRead)
   at Microsoft.PowerShell.PSConsoleReadLine.InputLoop()
   at Microsoft.PowerShell.PSConsoleReadLine.ReadLine(Runspace runspace, EngineIntrinsics engineIntrinsics, CancellationToken cancellationToken)

PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code> � kubectl set-context minikube : The term ''' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:1

PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code> kubectl config use-context minikube error: no context exists with the name: "minikube" PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code> kubectl config use-context minikube Switched to context "minikube". PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code> kubectl create namespace monitoring namespace/monitoring created PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code> kubectl apply -f prometheus-operator/ error: error reading [prometheus-operator/]: recognized file extensions are [.json .yaml .yml] PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code> kubectl apply -f prometheus-operator error: error reading [prometheus-operator]: recognized file extensions are [.json .yaml .yml] PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code> dir

Directory: C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code

Mode LastWriteTime Length Name

d----- 02/10/2024 09:03 demo-certs d----- 02/10/2024 09:03 minio d----- 02/10/2024 09:03 prometheus d----- 02/10/2024 09:03 prometheus-2 d----- 02/10/2024 09:03 prometheus-operator d----- 02/10/2024 09:03 prometheus-operator-crds d----- 02/10/2024 09:03 receiver-1 d----- 02/10/2024 09:03 receiver-2 d----- 02/10/2024 09:03 thanos d----- 02/10/2024 09:03 thanos-2 -a---- 02/10/2024 09:03 345 hashring.yaml -a---- 02/10/2024 09:03 138 macosenvironment.sh -a---- 02/10/2024 09:03 103 minio-ns.yaml -a---- 02/10/2024 09:03 263 minioapply.sh -a---- 02/10/2024 09:03 108 monitoring-ns.yaml -a---- 02/10/2024 09:03 96 portforward.sh -a---- 02/10/2024 09:03 2398 receiver-tls.yaml -a---- 02/10/2024 09:03 281 receiver-write-service.yaml

PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code> kubectl apply -f prometheus-operator error: error reading [prometheus-operator]: recognized file extensions are [.json .yaml .yml] PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code> cd .\prometheus-operator\ PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code\prometheus-operator> dir

Directory: C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code\prometheus-operator

Mode LastWriteTime Length Name

d----- 02/10/2024 09:03 deployment d----- 02/10/2024 09:03 rbac

PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code\prometheus-operator> cd .. PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code> kubectl apply -R -f prometheus-operator serviceaccount/prometheus-operator created clusterrole.rbac.authorization.k8s.io/prometheus-operator created clusterrolebinding.rbac.authorization.k8s.io/prometheus-operator created deployment.apps/prometheus-operator created clusterrole.rbac.authorization.k8s.io/prometheus-crd-view created clusterrole.rbac.authorization.k8s.io/prometheus-crd-edit created PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code> kubectl apply -f prometheus-thanos error: the path "prometheus-thanos" does not exist PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code> kubectl apply -f prometheus-thanos error: the path "prometheus-thanos" does not exist PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code> ls

Directory: C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code

Mode LastWriteTime Length Name

d----- 02/10/2024 09:03 demo-certs d----- 02/10/2024 09:03 minio d----- 02/10/2024 09:03 prometheus d----- 02/10/2024 09:03 prometheus-2 d----- 02/10/2024 09:03 prometheus-operator d----- 02/10/2024 09:03 prometheus-operator-crds d----- 02/10/2024 09:03 receiver-1 d----- 02/10/2024 09:03 receiver-2 d----- 02/10/2024 09:03 thanos d----- 02/10/2024 09:03 thanos-2 -a---- 02/10/2024 09:03 345 hashring.yaml -a---- 02/10/2024 09:03 138 macosenvironment.sh -a---- 02/10/2024 09:03 103 minio-ns.yaml -a---- 02/10/2024 09:03 263 minioapply.sh -a---- 02/10/2024 09:03 108 monitoring-ns.yaml -a---- 02/10/2024 09:03 96 portforward.sh -a---- 02/10/2024 09:03 2398 receiver-tls.yaml -a---- 02/10/2024 09:03 281 receiver-write-service.yaml

PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code> kubectl apply -f prometheus serviceaccount/prometheus created clusterrole.rbac.authorization.k8s.io/prometheus created clusterrolebinding.rbac.authorization.k8s.io/prometheus created secret/objstore created service/sidecar created secret/sidecar-tls created resource mapping not found for name: "staging" namespace: "monitoring" from "prometheus\3-prometheus.yaml": no matches for kind "Prometheus" in version "monitoring.coreos.com/v1" ensure CRDs are installed first resource mapping not found for name: "prometheus" namespace: "monitoring" from "prometheus\4-pod-monitor.yaml": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1" ensure CRDs are installed first PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code> kubectl apply -f .\prometheus-operator-crds\ customresourcedefinition.apiextensions.k8s.io/alertmanagerconfigs.monitoring.coreos.com created customresourcedefinition.apiextensions.k8s.io/alertmanagers.monitoring.coreos.com created customresourcedefinition.apiextensions.k8s.io/podmonitors.monitoring.coreos.com created customresourcedefinition.apiextensions.k8s.io/probes.monitoring.coreos.com created customresourcedefinition.apiextensions.k8s.io/prometheusrules.monitoring.coreos.com created customresourcedefinition.apiextensions.k8s.io/scrapeconfigs.monitoring.coreos.com created customresourcedefinition.apiextensions.k8s.io/servicemonitors.monitoring.coreos.com created customresourcedefinition.apiextensions.k8s.io/thanosrulers.monitoring.coreos.com created Error from server (Invalid): error when creating "prometheus-operator-crds\prometheusagents.yaml": CustomResourceDefinition.apiextensions.k8s.io "prometheusagents.monitoring.coreos.com" is invalid: metadata.annotations: Too long: must have at most 262144 bytes Error from server (Invalid): error when creating "prometheus-operator-crds\prometheuses.yaml": CustomResourceDefinition.apiextensions.k8s.io "prometheuses.monitoring.coreos.com" is invalid: metadata.annotations: Too long: must have at most 262144 bytes PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code> kubectl apply -f prometheus serviceaccount/prometheus unchanged clusterrole.rbac.authorization.k8s.io/prometheus unchanged clusterrolebinding.rbac.authorization.k8s.io/prometheus unchanged servicemonitor.monitoring.coreos.com/prometheus created secret/objstore configured service/sidecar unchanged secret/sidecar-tls configured error: resource mapping not found for name: "staging" namespace: "monitoring" from "prometheus\3-prometheus.yaml": no matches for kind "Prometheus" in version "monitoring.coreos.com/v1" ensure CRDs are installed first PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code> kubectl get pods -n monitoring NAME READY STATUS RESTARTS AGE prometheus-operator-6bb4bc6667-84l7c 1/1 Running 0 3m24s PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code>

rifaterdemsahin commented 1 day ago

gpt > fix > [] It seems you encountered multiple issues with setting up Prometheus and Thanos on your Kubernetes cluster using Minikube. Here are a few suggestions to address the problems:

1. Proxy Configuration for Minikube

Since Minikube had trouble accessing external images (! Failing to connect to https://registry.k8s.io/), ensure that your network environment (if behind a proxy) is configured correctly. You may need to set proxy variables within Minikube:

minikube start --docker-env HTTP_PROXY=http://<proxy>:<port> --docker-env HTTPS_PROXY=https://<proxy>:<port>

2. Special Character Issue in PowerShell

The exception is due to an emoji or special character that PowerShell failed to process:

System.Text.EncoderFallbackException: Unable to translate Unicode character \uD83D at index 0 to specified code page.

This can be caused by copying commands that include special characters. Simply re-type commands without using emojis or strange characters.

3. Correct kubectl Context Switch

You tried:

kubectl set-context minikube

But the correct command to switch contexts in kubectl is:

kubectl config use-context minikube

4. Prometheus Operator CRD Installation

Ensure that all CustomResourceDefinitions (CRDs) for Prometheus Operator are installed before applying Prometheus manifests:

kubectl apply -f ./prometheus-operator-crds/

Make sure that the CRDs do not exceed the metadata size limit, as seen in:

Error from server (Invalid): metadata.annotations: Too long: must have at most 262144 bytes

This issue is likely due to large annotations in the YAML files. Try reducing the size of annotations if possible.

5. Apply Prometheus YAML Files

After the CRDs are installed, retry applying the Prometheus manifests:

kubectl apply -f ./prometheus/

Ensure that the Prometheus CRDs are in place before applying the manifests for Prometheus.

6. Monitor the Status of Pods

Once everything is deployed, check the status of the Prometheus pods:

kubectl get pods -n monitoring

With these steps, your Minikube and Prometheus setup should work more smoothly. Let me know if further issues arise!

rifaterdemsahin commented 1 day ago

restart

# Set the kubectl context to minikube
kubectl config use-context minikube

# Delete the existing namespace if any
kubectl delete namespace monitoring

# Create the monitoring namespace
kubectl create namespace monitoring

# Install Prometheus Operator CustomResourceDefinitions (CRDs)
kubectl apply -f ./prometheus-operator-crds/

# Apply Prometheus manifests
kubectl apply -f ./prometheus/

# Check the status of Prometheus pods
kubectl get pods -n monitoring
rifaterdemsahin commented 1 day ago

Delete and Create has the same error >>> crd creation has the issues

PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code> kubectl config use-context minikube error: no context exists with the name: "minikube" PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code> kubectl config use-context minikube Switched to context "minikube". PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code> kubectl create namespace monitoring namespace/monitoring created PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code> kubectl apply -f prometheus-operator/ error: error reading [prometheus-operator/]: recognized file extensions are [.json .yaml .yml] PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code> kubectl apply -f prometheus-operator error: error reading [prometheus-operator]: recognized file extensions are [.json .yaml .yml] PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code> dir

Directory: C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code

Mode LastWriteTime Length Name

d----- 02/10/2024 09:03 demo-certs d----- 02/10/2024 09:03 minio d----- 02/10/2024 09:03 prometheus d----- 02/10/2024 09:03 prometheus-2 d----- 02/10/2024 09:03 prometheus-operator d----- 02/10/2024 09:03 prometheus-operator-crds d----- 02/10/2024 09:03 receiver-1 d----- 02/10/2024 09:03 receiver-2 d----- 02/10/2024 09:03 thanos d----- 02/10/2024 09:03 thanos-2 -a---- 02/10/2024 09:03 345 hashring.yaml -a---- 02/10/2024 09:03 138 macosenvironment.sh -a---- 02/10/2024 09:03 103 minio-ns.yaml -a---- 02/10/2024 09:03 263 minioapply.sh -a---- 02/10/2024 09:03 108 monitoring-ns.yaml -a---- 02/10/2024 09:03 96 portforward.sh -a---- 02/10/2024 09:03 2398 receiver-tls.yaml -a---- 02/10/2024 09:03 281 receiver-write-service.yaml

PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code> kubectl apply -f prometheus-operator error: error reading [prometheus-operator]: recognized file extensions are [.json .yaml .yml] PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code> cd .\prometheus-operator\ PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code\prometheus-operator> dir

Directory: C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code\prometheus-operator

Mode LastWriteTime Length Name

d----- 02/10/2024 09:03 deployment d----- 02/10/2024 09:03 rbac

PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code\prometheus-operator> cd .. PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code> kubectl apply -R -f prometheus-operator serviceaccount/prometheus-operator created clusterrole.rbac.authorization.k8s.io/prometheus-operator created clusterrolebinding.rbac.authorization.k8s.io/prometheus-operator created deployment.apps/prometheus-operator created clusterrole.rbac.authorization.k8s.io/prometheus-crd-view created clusterrole.rbac.authorization.k8s.io/prometheus-crd-edit created PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code> kubectl apply -f prometheus-thanos error: the path "prometheus-thanos" does not exist PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code> kubectl apply -f prometheus-thanos error: the path "prometheus-thanos" does not exist PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code> ls

Directory: C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code

Mode LastWriteTime Length Name

d----- 02/10/2024 09:03 demo-certs d----- 02/10/2024 09:03 minio d----- 02/10/2024 09:03 prometheus d----- 02/10/2024 09:03 prometheus-2 d----- 02/10/2024 09:03 prometheus-operator d----- 02/10/2024 09:03 prometheus-operator-crds d----- 02/10/2024 09:03 receiver-1 d----- 02/10/2024 09:03 receiver-2 d----- 02/10/2024 09:03 thanos d----- 02/10/2024 09:03 thanos-2 -a---- 02/10/2024 09:03 345 hashring.yaml -a---- 02/10/2024 09:03 138 macosenvironment.sh -a---- 02/10/2024 09:03 103 minio-ns.yaml -a---- 02/10/2024 09:03 263 minioapply.sh -a---- 02/10/2024 09:03 108 monitoring-ns.yaml -a---- 02/10/2024 09:03 96 portforward.sh -a---- 02/10/2024 09:03 2398 receiver-tls.yaml -a---- 02/10/2024 09:03 281 receiver-write-service.yaml

PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code> kubectl apply -f prometheus serviceaccount/prometheus created clusterrole.rbac.authorization.k8s.io/prometheus created clusterrolebinding.rbac.authorization.k8s.io/prometheus created secret/objstore created service/sidecar created secret/sidecar-tls created resource mapping not found for name: "staging" namespace: "monitoring" from "prometheus\3-prometheus.yaml": no matches for kind "Prometheus" in version "monitoring.coreos.com/v1" ensure CRDs are installed first resource mapping not found for name: "prometheus" namespace: "monitoring" from "prometheus\4-pod-monitor.yaml": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1" ensure CRDs are installed first PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code> kubectl apply -f .\prometheus-operator-crds\ customresourcedefinition.apiextensions.k8s.io/alertmanagerconfigs.monitoring.coreos.com created customresourcedefinition.apiextensions.k8s.io/alertmanagers.monitoring.coreos.com created customresourcedefinition.apiextensions.k8s.io/podmonitors.monitoring.coreos.com created customresourcedefinition.apiextensions.k8s.io/probes.monitoring.coreos.com created customresourcedefinition.apiextensions.k8s.io/prometheusrules.monitoring.coreos.com created customresourcedefinition.apiextensions.k8s.io/scrapeconfigs.monitoring.coreos.com created customresourcedefinition.apiextensions.k8s.io/servicemonitors.monitoring.coreos.com created customresourcedefinition.apiextensions.k8s.io/thanosrulers.monitoring.coreos.com created Error from server (Invalid): error when creating "prometheus-operator-crds\prometheusagents.yaml": CustomResourceDefinition.apiextensions.k8s.io "prometheusagents.monitoring.coreos.com" is invalid: metadata.annotations: Too long: must have at most 262144 bytes Error from server (Invalid): error when creating "prometheus-operator-crds\prometheuses.yaml": CustomResourceDefinition.apiextensions.k8s.io "prometheuses.monitoring.coreos.com" is invalid: metadata.annotations: Too long: must have at most 262144 bytes PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code> kubectl apply -f prometheus serviceaccount/prometheus unchanged clusterrole.rbac.authorization.k8s.io/prometheus unchanged clusterrolebinding.rbac.authorization.k8s.io/prometheus unchanged servicemonitor.monitoring.coreos.com/prometheus created secret/objstore configured service/sidecar unchanged secret/sidecar-tls configured error: resource mapping not found for name: "staging" namespace: "monitoring" from "prometheus\3-prometheus.yaml": no matches for kind "Prometheus" in version "monitoring.coreos.com/v1" ensure CRDs are installed first PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code> kubectl get pods -n monitoring NAME READY STATUS RESTARTS AGE prometheus-operator-6bb4bc6667-84l7c 1/1 Running 0 3m24s PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code> kubectl get pods -n monitoring NAME READY STATUS RESTARTS AGE prometheus-operator-6bb4bc6667-84l7c 1/1 Running 0 7m34s PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code> kubectl config use-context minikube Switched to context "minikube". PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code> kubectl delete namespace monitoring namespace "monitoring" deleted PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code>

kubectl create namespace monitoring namespace/monitoring created PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code> kubectl apply -f ./prometheus-operator-crds customresourcedefinition.apiextensions.k8s.io/alertmanagerconfigs.monitoring.coreos.com configured customresourcedefinition.apiextensions.k8s.io/alertmanagers.monitoring.coreos.com configured customresourcedefinition.apiextensions.k8s.io/podmonitors.monitoring.coreos.com configured customresourcedefinition.apiextensions.k8s.io/probes.monitoring.coreos.com configured customresourcedefinition.apiextensions.k8s.io/prometheusrules.monitoring.coreos.com configured customresourcedefinition.apiextensions.k8s.io/scrapeconfigs.monitoring.coreos.com configured customresourcedefinition.apiextensions.k8s.io/servicemonitors.monitoring.coreos.com configured customresourcedefinition.apiextensions.k8s.io/thanosrulers.monitoring.coreos.com configured Error from server (Invalid): error when creating "prometheus-operator-crds\prometheusagents.yaml": CustomResourceDefinition.apiextensions.k8s.io "prometheusagents.monitoring.coreos.com" is invalid: metadata.annotations: Too long: must have at most 262144 bytes Error from server (Invalid): error when creating "prometheus-operator-crds\prometheuses.yaml": CustomResourceDefinition.apiextensions.k8s.io "prometheuses.monitoring.coreos.com" is invalid: metadata.annotations: Too long: must have at most 262144 bytes PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code> kubectl apply -R -f prometheus-operator/ serviceaccount/prometheus-operator created clusterrole.rbac.authorization.k8s.io/prometheus-operator unchanged clusterrolebinding.rbac.authorization.k8s.io/prometheus-operator unchanged deployment.apps/prometheus-operator created clusterrole.rbac.authorization.k8s.io/prometheus-crd-view unchanged clusterrole.rbac.authorization.k8s.io/prometheus-crd-edit unchanged PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code> kubectl apply -f prometheus serviceaccount/prometheus created clusterrole.rbac.authorization.k8s.io/prometheus unchanged clusterrolebinding.rbac.authorization.k8s.io/prometheus unchanged servicemonitor.monitoring.coreos.com/prometheus created secret/objstore created service/sidecar created secret/sidecar-tls created error: resource mapping not found for name: "staging" namespace: "monitoring" from "prometheus\3-prometheus.yaml": no matches for kind "Prometheus" in version "monitoring.coreos.com/v1" ensure CRDs are installed first PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code> kubectl get pods -n monitoring NAME READY STATUS RESTARTS AGE prometheus-operator-6bb4bc6667-26j5s 1/1 Running 0 22s PS C:\projects\PrometheusRemoteWrite2\prometheusremotewrite\code>

rifaterdemsahin commented 1 day ago

first crd than operator image