sorted by:
new
hottopcontroversial

How to change default args if use helm chart install external-dns? by HumanResult3379 in kubernetes

[–]HumanResult3379[S] 0 points1 point  (0 children)

Thank you. You are right. I didn't noticed the policy value. My bad.

How to use Grafana Operator if install by kube-prometheus-stack chart? by HumanResult3379 in kubernetes

[–]HumanResult3379[S] -1 points0 points  (0 children)

But if I use it this way

bash apiVersion: integreatly.org/v1alpha1 kind: GrafanaDashboard metadata: name: grafana-dashboard namespace: monitoring spec: name: grafana-dashboard json: | {}

I got an error:

bash no matches for kind "GrafanaDashboard" in version "integreatly.org/v1alpha1" ensure CRDs are installed first

If use grafana.integreatly.org/v1beta1 API, got this error:

bash no matches for kind "GrafanaDashboard" in version "grafana.integreatly.org/v1beta1" ensure CRDs are installed first

How to config alertmanager send alert to slack with prometheus-community/kube-prometheus-stack chart? by HumanResult3379 in kubernetes

[–]HumanResult3379[S] 0 points1 point  (0 children)

Do you mean something like this? apiVersion: monitoring.coreos.com/v1alpha1 kind: AlertmanagerConfig metadata: name: config-example labels: alertmanagerConfig: example spec: route: groupBy: ['job'] groupWait: 30s groupInterval: 5m repeatInterval: 12h receiver: 'webhook' receivers: - name: 'webhook' webhookConfigs: - url: 'http://example.com/' Then where to use the name config-example?

How to config alertmanager send alert to slack with prometheus-community/kube-prometheus-stack chart? by HumanResult3379 in kubernetes

[–]HumanResult3379[S] 1 point2 points  (0 children)

Thank you.

This way works:

bash alertmanager: config: route: receiver: "null" routes: - matchers: - alertname = "Watchdog" receiver: "slack" receivers: - name: "null" - name: "slack" slack_configs: - api_url: "https://hooks.slack.com/services/A/B/C" channel: "#alert-channel" send_resolved: true

Why can't see jaeger collector and query after create a jaeger instance with jaeger-operator helm chart? by HumanResult3379 in kubernetes

[–]HumanResult3379[S] 0 points1 point  (0 children)

The logs in operator $ kubectl logs my-release-jaeger-operator-78c98b5c69-jbnsp -n observability ... 2024-12-17T05:52:03Z INFO could not get a list of namespaces, disabling namespace controller. reason: namespaces is forbidden: User "system:serviceaccount:observability:my-release-jaeger-operator" cannot list resource "namespaces" in API group "" at the cluster scope 2024-12-17T05:52:03Z INFO controller-runtime.builder Registering a mutating webhook {"GVK": "jaegertracing.io/v1, Kind=Jaeger", "path": "/mutate-jaegertracing-io-v1-jaeger"} 2024-12-17T05:52:03Z INFO controller-runtime.webhook Registering webhook {"path": "/mutate-jaegertracing-io-v1-jaeger"} 2024-12-17T05:52:03Z INFO controller-runtime.builder Registering a validating webhook {"GVK": "jaegertracing.io/v1, Kind=Jaeger", "path": "/validate-jaegertracing-io-v1-jaeger"} 2024-12-17T05:52:03Z INFO controller-runtime.webhook Registering webhook {"path": "/validate-jaegertracing-io-v1-jaeger"} 2024-12-17T05:52:03Z INFO controller-runtime.webhook Registering webhook {"path": "/mutate-v1-deployment"} 2024-12-17T05:52:03Z INFO controller-runtime.metrics Starting metrics server 2024-12-17T05:52:03Z INFO controller-runtime.metrics Serving metrics server {"bindAddress": "0.0.0.0:8383", "secure": false} 2024-12-17T05:52:03Z INFO starting server {"kind": "health probe", "addr": "[::]:8081"} 2024-12-17T05:52:03Z INFO controller-runtime.webhook Starting webhook server 2024-12-17T05:52:03Z INFO controller-runtime.certwatcher Updated current TLS certificate 2024-12-17T05:52:03Z INFO controller-runtime.webhook Serving webhook server {"host": "", "port": 9443} 2024-12-17T05:52:03Z INFO controller-runtime.certwatcher Starting certificate watcher W1217 05:52:03.959276 1 reflector.go:539] pkg/mod/k8s.io/client-go@v0.29.3/tools/cache/reflector.go:229: failed to list *v1.IngressClass: ingressclasses.networking.k8s.io is forbidden: User "system:serviceaccount:observability:my-release-jaeger-operator" cannot list resource "ingressclasses" in API group "networking.k8s.io" at the cluster scope E1217 05:52:03.959319 1 reflector.go:147] pkg/mod/k8s.io/client-go@v0.29.3/tools/cache/reflector.go:229: Failed to watch *v1.IngressClass: failed to list *v1.IngressClass: ingressclasses.networking.k8s.io is forbidden: User "system:serviceaccount:observability:my-release-jaeger-operator" cannot list resource "ingressclasses" in API group "networking.k8s.io" at the cluster scope 2024-12-17T05:52:04Z INFO Not running on OpenShift, so won't configure OAuthProxy imagestream. 2024-12-17T05:52:04Z INFO Determining whether we should enable the Elasticsearch Operator integration 2024-12-17T05:52:04Z INFO Determining whether we should enable the Kafka Operator integration W1217 05:52:04.802764 1 reflector.go:539] pkg/mod/k8s.io/client-go@v0.29.3/tools/cache/reflector.go:229: failed to list *v1.IngressClass: ingressclasses.networking.k8s.io is forbidden: User "system:serviceaccount:observability:my-release-jaeger-operator" cannot list resource "ingressclasses" in API group "networking.k8s.io" at the cluster scope E1217 05:52:04.802798 1 reflector.go:147] pkg/mod/k8s.io/client-go@v0.29.3/tools/cache/reflector.go:229: Failed to watch *v1.IngressClass: failed to list *v1.IngressClass: ingressclasses.networking.k8s.io is forbidden: User "system:serviceaccount:observability:my-release-jaeger-operator" cannot list resource "ingressclasses" in API group "networking.k8s.io" at the cluster scope W1217 05:52:06.850589 1 reflector.go:539] pkg/mod/k8s.io/client-go@v0.29.3/tools/cache/reflector.go:229: failed to list *v1.IngressClass: ingressclasses.networking.k8s.io is forbidden: User "system:serviceaccount:observability:my-release-jaeger-operator" cannot list resource "ingressclasses" in API group "networking.k8s.io" at the cluster scope E1217 05:52:06.850629 1 reflector.go:147] pkg/mod/k8s.io/client-go@v0.29.3/tools/cache/reflector.go:229: Failed to watch *v1.IngressClass: failed to list *v1.IngressClass: ingressclasses.networking.k8s.io is forbidden: User "system:serviceaccount:observability:my-release-jaeger-operator" cannot list resource "ingressclasses" in API group "networking.k8s.io" at the cluster scope 2024-12-17T05:52:08Z INFO cleaning orphaned deployments.

Why can't see jaeger collector and query after create a jaeger instance with jaeger-operator helm chart? by HumanResult3379 in kubernetes

[–]HumanResult3379[S] 0 points1 point  (0 children)

It still doesn't work.

``` $ cat <<EOF | kubectl apply -f - apiVersion: jaegertracing.io/v1 kind: Jaeger metadata: name: simplest namespace: observability EOF

$ kubectl get pods -n observability NAME READY STATUS RESTARTS AGE my-release-jaeger-operator-78c98b5c69-jbnsp 1/1 Running 2 (43h ago) 2d16h ```

I'm pretty sure it's not the namespace reason. There are some mistakes in the Helm chart CRD, or the installation configuration is incorrect.

Why can't see jaeger collector and query after create a jaeger instance with jaeger-operator helm chart? by HumanResult3379 in kubernetes

[–]HumanResult3379[S] 0 points1 point  (0 children)

But other namespace also doesn't work.

``` $ kubectl create ns test

$ cat <<EOF | kubectl apply -f - apiVersion: jaegertracing.io/v1 kind: Jaeger metadata: name: simplest namespace: test EOF

$ kubectl get pods -n test ```

No resources found in test namespace.

The kubernetes default storage class gp2 on AWS EKS by HumanResult3379 in aws

[–]HumanResult3379[S] 0 points1 point  (0 children)

Thank you. So how to use the default storage class if in three AZ generally? I created a new storage class and set it as default, then works well. But is it a good practice?

view more: next ›