[operator] "mopentelemetrycollectorbeta.kb.io": failed to call webhook / "opentelemetry-operator-webhook-service" not foud

It's been a week since I last tried to deploy my environment with OpenTelemetry installed, and now I'm getting a close one error when i try to deploy my helm
This is close of what my template generate :
apiVersion: opentelemetry.io/v1beta1
kind: OpenTelemetryCollector
metadata:
  name: opentelemetry-collector
spec:
  mode: deployment
  serviceAccount: opentelemetry-operator
  config:
    receivers:
      otlp:
        protocols:
          grpc:
            endpoint: <IP_ADDRESS>:4317
          http:
            endpoint: <IP_ADDRESS>:4318
    exporters:
      otlp:
        endpoint: <IP_ADDRESS>:4317
        tls:
          insecure: true
    processors:
      batch:

(I can't deploy a simple collector like this..)
Error from server (InternalError): Internal error occurred: failed calling webhook "mopentelemetrycollectorbeta.kb.io": failed to call webhook: Post "https://opentelemetry-operator-webhook-service.opentelemetry-operator-system.svc:443/mutate-opentelemetry-io-v1beta1-opentelemetrycollector?timeout=10s": service "opentelemetry-operator-webhook-service" not found

I have tried to make a clean install of a k3s cluster and re make all the step one by one of this documentation but when i try to apply the yml provided it doesn't work..
IDK if it's related with the issue : https://github.com/open-telemetry/opentelemetry-helm-charts/issues/1199 but i prefer to create another one to not put trash inside it

IMHO it may be useful to show helm values too. If they're similar to mine it may be better to collapse the issues into one.

 Migrate to v1beta1.
Error from server (InternalError): error when creating "test.yml": Internal error occurred: Internal error occurred: conversion webhook for opentelemetry.io/v1alpha1, Kind=OpenTelemetryCollector failed: the server could not find the requested resource

I patched it:
apiVersion: opentelemetry.io/v1beta1
kind: OpenTelemetryCollector
metadata:
  name: my-incredible-otel # Otel add -collector to the name
  labels:
    app.kubernetes.io/name: otel
    app.kubernetes.io/component: otel-collector
spec:
  mode: deployment
  serviceAccount: opentelemetry-operator
  config:
    receivers:
      otlp:
        protocols:
          grpc:
            endpoint: <IP_ADDRESS>:4317
          http:
            endpoint: <IP_ADDRESS>:4318
    exporters:
      otlp:
        endpoint: x.x.x.x:5555
        tls:
          insecure: true
    processors:
      batch:
    service:
      pipelines:
        traces:
          receivers: [otlp]
          processors: [batch]
          exporters: [otlp]
        metrics:
          receivers: [otlp]
          processors: [batch]
          exporters: [otlp]
        logs:
          receivers: [otlp]
          processors: [batch]
          exporters: [otlp]

> kubectl apply -f test.yml -n my-second-namespace
Error from server (InternalError): error when creating "test.yml": Internal error occurred: failed calling webhook "mopentelemetrycollectorbeta.kb.io": failed to call webhook: Post "https://opentelemetry-operator-webhook-service.opentelemetry-operator-system.svc:443/mutate-opentelemetry-io-v1beta1-opentelemetrycollector?timeout=10s": service "opentelemetry-operator-webhook-service" not found

I think we are in the same boat.

@PandeoF1 can you check that the service exists? My guess is the webhooks are misconfigured somehow. Have you upgraded the CRDs per the instructions here?

@PandeoF1 can you check that the service exists? My guess is the webhooks are misconfigured somehow. Have you upgraded the CRDs per the instructions here?

For the services i will look that tomorrow.
For the CRDs i have made a clean install so i shouldn't need to update it i think ?

yep, let me know. If you did a clean CRD install you should be okay. I also will have time tomorrow if you'd like to pair on this :)

IDK why but the opentelemetrycollectors CRD is red in K9s. (It's possibly related to my issue :/)

To be sure i have do the step of the CRD upgrade :
> kubectl patch customresourcedefinitions opentelemetrycollectors.opentelemetry.io  \
  --subresource='status' \
  --type='merge' \
  -p '{"status":{"storedVersions":["v1beta1"]}}'
customresourcedefinition.apiextensions.k8s.io/opentelemetrycollectors.opentelemetry.io patched (no change)

kubectl describe crd opentelemetrycollectors.opentelemetry.io :

https://gist.github.com/PandeoF1/c286feb765afddf6db1d281c07bfbf3a

Could my problem be related to the fact that the opentelemetry-helm-charts repo is behind the opentelemetry-operator repo? (i talk about the version)

as long as the version of your operator matches that of the helm version (i.e. helm's application version is 0.xxx.y and your operation version is 0.xxx.y) you should be okay...
It definitely seems like the service exists and is in the right namespace. I noticed there were some restarts for your operator. Did the logs have anything to say?

log of operator :
{"level":"INFO","timestamp":"2024-05-29T12:46:06.00301489Z","message":"Starting the OpenTelemetry Operator","opentelemetry-operator":"0.101.0","opentelemetry-collector":"ghcr.io/open-telemetry/opentelemetry-collector-releases/opentelemetry-collector:0.101.0","opentelemetry-targetallocator":"ghcr.io/open-telemetry/opentelemetry-operator/target-allocator:0.101.0","operator-opamp-bridge":"ghcr.io/open-telemetry/opentelemetry-operator/operator-opamp-bridge:0.101.0","auto-instrumentation-java":"ghcr.io/open-telemetry/opentelemetry-operator/autoinstrumentation-java:1.32.1","auto-instrumentation-nodejs":"ghcr.io/open-telemetry/opentelemetry-operator/autoinstrumentation-nodejs:0.51.0","auto-instrumentation-python":"ghcr.io/open-telemetry/opentelemetry-operator/autoinstrumentation-python:0.44b0","auto-instrumentation-dotnet":"ghcr.io/open-telemetry/opentelemetry-operator/autoinstrumentation-dotnet:1.2.0","auto-instrumentation-go":"ghcr.io/open-telemetry/opentelemetry-go-instrumentation/autoinstrumentation-go:v0.12.0-alpha","auto-instrumentation-apache-httpd":"ghcr.io/open-telemetry/opentelemetry-operator/autoinstrumentation-apache-httpd:1.0.4","auto-instrumentation-nginx":"ghcr.io/open-telemetry/opentelemetry-operator/autoinstrumentation-apache-httpd:1.0.4","feature-gates":"-operator.golang.flags,operator.observability.prometheus","build-date":"2024-05-29T12:23:02Z","go-version":"go1.21.10","go-arch":"amd64","go-os":"linux","labels-filter":],"annotations-filter":],"enable-multi-instrumentation":false,"enable-apache-httpd-instrumentation":true,"enable-dotnet-instrumentation":true,"enable-go-instrumentation":false,"enable-python-instrumentation":true,"enable-nginx-instrumentation":true,"enable-nodejs-instrumentation":true,"enable-java-instrumentation":true,"zap-message-key":"message","zap-level-key":"level","zap-time-key":"timestamp","zap-level-format":"uppercase"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.003314379Z","logger":"setup","message":"the env var WATCH_NAMESPACE isn't set, watching all namespaces"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.031703509Z","logger":"setup","message":"Prometheus CRDs are installed, adding to scheme."}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.0318552Z","logger":"setup","message":"Openshift CRDs are not installed, skipping adding to scheme."}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.031994787Z","logger":"controller-runtime.builder","message":"Registering a mutating webhook","GVK":"opentelemetry.io/v1beta1, Kind=OpenTelemetryCollector","path":"/mutate-opentelemetry-io-v1beta1-opentelemetrycollector"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.032069506Z","logger":"controller-runtime.webhook","message":"Registering webhook","path":"/mutate-opentelemetry-io-v1beta1-opentelemetrycollector"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.03209653Z","logger":"controller-runtime.builder","message":"Registering a validating webhook","GVK":"opentelemetry.io/v1beta1, Kind=OpenTelemetryCollector","path":"/validate-opentelemetry-io-v1beta1-opentelemetrycollector"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.032133727Z","logger":"controller-runtime.webhook","message":"Registering webhook","path":"/validate-opentelemetry-io-v1beta1-opentelemetrycollector"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.032216992Z","logger":"controller-runtime.webhook","message":"Registering webhook","path":"/convert"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.032222507Z","logger":"controller-runtime.builder","message":"Conversion webhook enabled","GVK":"opentelemetry.io/v1beta1, Kind=OpenTelemetryCollector"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.032260204Z","logger":"controller-runtime.builder","message":"Registering a mutating webhook","GVK":"opentelemetry.io/v1alpha1, Kind=Instrumentation","path":"/mutate-opentelemetry-io-v1alpha1-instrumentation"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.032295487Z","logger":"controller-runtime.webhook","message":"Registering webhook","path":"/mutate-opentelemetry-io-v1alpha1-instrumentation"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.032321086Z","logger":"controller-runtime.builder","message":"Registering a validating webhook","GVK":"opentelemetry.io/v1alpha1, Kind=Instrumentation","path":"/validate-opentelemetry-io-v1alpha1-instrumentation"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.032361258Z","logger":"controller-runtime.webhook","message":"Registering webhook","path":"/validate-opentelemetry-io-v1alpha1-instrumentation"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.032452672Z","logger":"controller-runtime.webhook","message":"Registering webhook","path":"/mutate-v1-pod"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.032479348Z","logger":"controller-runtime.builder","message":"Registering a mutating webhook","GVK":"opentelemetry.io/v1alpha1, Kind=OpAMPBridge","path":"/mutate-opentelemetry-io-v1alpha1-opampbridge"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.032512744Z","logger":"controller-runtime.webhook","message":"Registering webhook","path":"/mutate-opentelemetry-io-v1alpha1-opampbridge"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.032535019Z","logger":"controller-runtime.builder","message":"Registering a validating webhook","GVK":"opentelemetry.io/v1alpha1, Kind=OpAMPBridge","path":"/validate-opentelemetry-io-v1alpha1-opampbridge"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.032566556Z","logger":"controller-runtime.webhook","message":"Registering webhook","path":"/validate-opentelemetry-io-v1alpha1-opampbridge"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.032593391Z","logger":"setup","message":"starting manager"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.032648419Z","logger":"controller-runtime.metrics","message":"Starting metrics server"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.032682855Z","message":"starting server","kind":"health probe","addr":":8081"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.032729689Z","logger":"controller-runtime.webhook","message":"Starting webhook server"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.032734287Z","logger":"controller-runtime.metrics","message":"Serving metrics server","bindAddress":"<IP_ADDRESS>:8080","secure":false}
I0529 12:46:06.032904       1 leaderelection.go:250] attempting to acquire leader lease opentelemetry-operator-system/9f7554c3.opentelemetry.io...
{"level":"INFO","timestamp":"2024-05-29T12:46:06.033267798Z","logger":"controller-runtime.certwatcher","message":"Updated current TLS certificate"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.033327932Z","logger":"controller-runtime.webhook","message":"Serving webhook server","host":"","port":9443}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.033374432Z","logger":"controller-runtime.certwatcher","message":"Starting certificate watcher"}
I0529 12:46:06.038009       1 leaderelection.go:260] successfully acquired lease opentelemetry-operator-system/9f7554c3.opentelemetry.io
{"level":"INFO","timestamp":"2024-05-29T12:46:06.038163131Z","logger":"collector-upgrade","message":"looking for managed instances to upgrade"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.038227482Z","logger":"instrumentation-upgrade","message":"looking for managed Instrumentation instances to upgrade"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.038265294Z","message":"Starting EventSource","controller":"opentelemetrycollector","controllerGroup":"opentelemetry.io","controllerKind":"OpenTelemetryCollector","source":"kind source: *v1beta1.OpenTelemetryCollector"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.038298702Z","message":"Starting EventSource","controller":"opentelemetrycollector","controllerGroup":"opentelemetry.io","controllerKind":"OpenTelemetryCollector","source":"kind source: *v1.ConfigMap"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.038311229Z","message":"Starting EventSource","controller":"opentelemetrycollector","controllerGroup":"opentelemetry.io","controllerKind":"OpenTelemetryCollector","source":"kind source: *v1.ServiceAccount"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.038319625Z","message":"Starting EventSource","controller":"opentelemetrycollector","controllerGroup":"opentelemetry.io","controllerKind":"OpenTelemetryCollector","source":"kind source: *v1.Service"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.038326577Z","message":"Starting EventSource","controller":"opentelemetrycollector","controllerGroup":"opentelemetry.io","controllerKind":"OpenTelemetryCollector","source":"kind source: *v1.Deployment"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.038323233Z","message":"Starting EventSource","controller":"opampbridge","controllerGroup":"opentelemetry.io","controllerKind":"OpAMPBridge","source":"kind source: *v1alpha1.OpAMPBridge"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.038333427Z","message":"Starting EventSource","controller":"opentelemetrycollector","controllerGroup":"opentelemetry.io","controllerKind":"OpenTelemetryCollector","source":"kind source: *v1.DaemonSet"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.03834086Z","message":"Starting EventSource","controller":"opentelemetrycollector","controllerGroup":"opentelemetry.io","controllerKind":"OpenTelemetryCollector","source":"kind source: *v1.StatefulSet"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.038342099Z","message":"Starting EventSource","controller":"opampbridge","controllerGroup":"opentelemetry.io","controllerKind":"OpAMPBridge","source":"kind source: *v1.ConfigMap"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.038348632Z","message":"Starting EventSource","controller":"opentelemetrycollector","controllerGroup":"opentelemetry.io","controllerKind":"OpenTelemetryCollector","source":"kind source: *v1.PersistentVolume"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.038355436Z","message":"Starting EventSource","controller":"opentelemetrycollector","controllerGroup":"opentelemetry.io","controllerKind":"OpenTelemetryCollector","source":"kind source: *v1.PersistentVolumeClaim"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.03836174Z","message":"Starting EventSource","controller":"opentelemetrycollector","controllerGroup":"opentelemetry.io","controllerKind":"OpenTelemetryCollector","source":"kind source: *v1.Ingress"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.038372982Z","message":"Starting EventSource","controller":"opentelemetrycollector","controllerGroup":"opentelemetry.io","controllerKind":"OpenTelemetryCollector","source":"kind source: *v2.HorizontalPodAutoscaler"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.038381697Z","message":"Starting EventSource","controller":"opentelemetrycollector","controllerGroup":"opentelemetry.io","controllerKind":"OpenTelemetryCollector","source":"kind source: *v1.PodDisruptionBudget"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.038355132Z","message":"Starting EventSource","controller":"opampbridge","controllerGroup":"opentelemetry.io","controllerKind":"OpAMPBridge","source":"kind source: *v1.ServiceAccount"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.038387403Z","message":"Starting EventSource","controller":"opentelemetrycollector","controllerGroup":"opentelemetry.io","controllerKind":"OpenTelemetryCollector","source":"kind source: *v1.ServiceMonitor"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.038392989Z","message":"Starting EventSource","controller":"opentelemetrycollector","controllerGroup":"opentelemetry.io","controllerKind":"OpenTelemetryCollector","source":"kind source: *v1.PodMonitor"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.038397159Z","message":"Starting Controller","controller":"opentelemetrycollector","controllerGroup":"opentelemetry.io","controllerKind":"OpenTelemetryCollector"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.038399978Z","message":"Starting EventSource","controller":"opampbridge","controllerGroup":"opentelemetry.io","controllerKind":"OpAMPBridge","source":"kind source: *v1.Service"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.038426865Z","message":"Starting EventSource","controller":"opampbridge","controllerGroup":"opentelemetry.io","controllerKind":"OpAMPBridge","source":"kind source: *v1.Deployment"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.038436648Z","message":"Starting Controller","controller":"opampbridge","controllerGroup":"opentelemetry.io","controllerKind":"OpAMPBridge"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.139826469Z","logger":"collector-upgrade","message":"no instances to upgrade"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.150493776Z","logger":"instrumentation-upgrade","message":"no instances to upgrade"}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.151804391Z","message":"Starting workers","controller":"opampbridge","controllerGroup":"opentelemetry.io","controllerKind":"OpAMPBridge","worker count":1}
{"level":"INFO","timestamp":"2024-05-29T12:46:06.155302182Z","message":"Starting workers","controller":"opentelemetrycollector","controllerGroup":"opentelemetry.io","controllerKind":"OpenTelemetryCollector","worker count":1}

There is 0 event inside the both namespace (operator-system and the one where i want to deploy the collector)

I have made another clean install to have a warning that are not present in the previous log and there it is :
{"level":"info","ts":"2024-05-29T14:02:55Z","msg":"Starting the OpenTelemetry Operator","opentelemetry-operator":"0.93.0","opentelemetry-collector":"my-registry.my-website.com/open-telemetry/opentelemetry-collector:0.101.0","opentelemetry-targetallocator":"ghcr.io/open-telemetry/opentelemetry-operator/target-allocator:0.93.0","operator-opamp-bridge":"ghcr.io/open-telemetry/opentelemetry-operator/operator-opamp-bridge:0.93.0","auto-instrumentation-java":"ghcr.io/open-telemetry/opentelemetry-operator/autoinstrumentation-java:1.32.0","auto-instrumentation-nodejs":"ghcr.io/open-telemetry/opentelemetry-operator/autoinstrumentation-nodejs:0.46.0","auto-instrumentation-python":"ghcr.io/open-telemetry/opentelemetry-operator/autoinstrumentation-python:0.43b0","auto-instrumentation-dotnet":"ghcr.io/open-telemetry/opentelemetry-operator/autoinstrumentation-dotnet:1.2.0","auto-instrumentation-go":"ghcr.io/open-telemetry/opentelemetry-go-instrumentation/autoinstrumentation-go:v0.10.1-alpha","auto-instrumentation-apache-httpd":"ghcr.io/open-telemetry/opentelemetry-operator/autoinstrumentation-apache-httpd:1.0.4","auto-instrumentation-nginx":"ghcr.io/open-telemetry/opentelemetry-operator/autoinstrumentation-apache-httpd:1.0.4","feature-gates":"operator.autoinstrumentation.apache-httpd,operator.autoinstrumentation.dotnet,-operator.autoinstrumentation.go,operator.autoinstrumentation.java,-operator.autoinstrumentation.multi-instrumentation,-operator.autoinstrumentation.nginx,operator.autoinstrumentation.nodejs,operator.autoinstrumentation.python,operator.collector.rewritetargetallocator,-operator.observability.prometheus","build-date":"2024-02-02T17:52:35Z","go-version":"go1.21.6","go-arch":"amd64","go-os":"linux","labels-filter":]}
{"level":"info","ts":"2024-05-29T14:02:55Z","logger":"setup","msg":"the env var WATCH_NAMESPACE isn't set, watching all namespaces"}
{"level":"info","ts":"2024-05-29T14:02:55Z","logger":"controller-runtime.builder","msg":"Registering a mutating webhook","GVK":"opentelemetry.io/v1alpha1, Kind=OpenTelemetryCollector","path":"/mutate-opentelemetry-io-v1alpha1-opentelemetrycollector"}
{"level":"info","ts":"2024-05-29T14:02:55Z","logger":"controller-runtime.webhook","msg":"Registering webhook","path":"/mutate-opentelemetry-io-v1alpha1-opentelemetrycollector"}
{"level":"info","ts":"2024-05-29T14:02:55Z","logger":"controller-runtime.builder","msg":"Registering a validating webhook","GVK":"opentelemetry.io/v1alpha1, Kind=OpenTelemetryCollector","path":"/validate-opentelemetry-io-v1alpha1-opentelemetrycollector"}
{"level":"info","ts":"2024-05-29T14:02:55Z","logger":"controller-runtime.webhook","msg":"Registering webhook","path":"/validate-opentelemetry-io-v1alpha1-opentelemetrycollector"}
{"level":"info","ts":"2024-05-29T14:02:55Z","logger":"controller-runtime.builder","msg":"Registering a mutating webhook","GVK":"opentelemetry.io/v1alpha1, Kind=Instrumentation","path":"/mutate-opentelemetry-io-v1alpha1-instrumentation"}
{"level":"info","ts":"2024-05-29T14:02:55Z","logger":"controller-runtime.webhook","msg":"Registering webhook","path":"/mutate-opentelemetry-io-v1alpha1-instrumentation"}
{"level":"info","ts":"2024-05-29T14:02:55Z","logger":"controller-runtime.builder","msg":"Registering a validating webhook","GVK":"opentelemetry.io/v1alpha1, Kind=Instrumentation","path":"/validate-opentelemetry-io-v1alpha1-instrumentation"}
{"level":"info","ts":"2024-05-29T14:02:55Z","logger":"controller-runtime.webhook","msg":"Registering webhook","path":"/validate-opentelemetry-io-v1alpha1-instrumentation"}
{"level":"info","ts":"2024-05-29T14:02:55Z","logger":"controller-runtime.webhook","msg":"Registering webhook","path":"/mutate-v1-pod"}
{"level":"info","ts":"2024-05-29T14:02:55Z","logger":"controller-runtime.builder","msg":"Registering a mutating webhook","GVK":"opentelemetry.io/v1alpha1, Kind=OpAMPBridge","path":"/mutate-opentelemetry-io-v1alpha1-opampbridge"}
{"level":"info","ts":"2024-05-29T14:02:55Z","logger":"controller-runtime.webhook","msg":"Registering webhook","path":"/mutate-opentelemetry-io-v1alpha1-opampbridge"}
{"level":"info","ts":"2024-05-29T14:02:55Z","logger":"controller-runtime.builder","msg":"Registering a validating webhook","GVK":"opentelemetry.io/v1alpha1, Kind=OpAMPBridge","path":"/validate-opentelemetry-io-v1alpha1-opampbridge"}
{"level":"info","ts":"2024-05-29T14:02:55Z","logger":"controller-runtime.webhook","msg":"Registering webhook","path":"/validate-opentelemetry-io-v1alpha1-opampbridge"}
{"level":"info","ts":"2024-05-29T14:02:55Z","logger":"setup","msg":"starting manager"}
{"level":"info","ts":"2024-05-29T14:02:55Z","logger":"controller-runtime.webhook","msg":"Starting webhook server"}
{"level":"info","ts":"2024-05-29T14:02:55Z","msg":"starting server","kind":"health probe","addr":":8081"}
{"level":"info","ts":"2024-05-29T14:02:55Z","logger":"controller-runtime.metrics","msg":"Starting metrics server"}
{"level":"info","ts":"2024-05-29T14:02:55Z","logger":"controller-runtime.metrics","msg":"Serving metrics server","bindAddress":"<IP_ADDRESS>:8080","secure":false}
I0529 14:02:55.705794       1 leaderelection.go:250] attempting to acquire leader lease opentelemetry-operator-system/9f7554c3.opentelemetry.io...
{"level":"info","ts":"2024-05-29T14:02:55Z","logger":"controller-runtime.certwatcher","msg":"Updated current TLS certificate"}
{"level":"info","ts":"2024-05-29T14:02:55Z","logger":"controller-runtime.webhook","msg":"Serving webhook server","host":"","port":9443}
{"level":"info","ts":"2024-05-29T14:02:55Z","logger":"controller-runtime.certwatcher","msg":"Starting certificate watcher"}
I0529 14:02:55.809131       1 leaderelection.go:260] successfully acquired lease opentelemetry-operator-system/9f7554c3.opentelemetry.io
{"level":"info","ts":"2024-05-29T14:02:55Z","logger":"collector-upgrade","msg":"looking for managed instances to upgrade"}
{"level":"info","ts":"2024-05-29T14:02:55Z","logger":"instrumentation-upgrade","msg":"looking for managed Instrumentation instances to upgrade"}
{"level":"info","ts":"2024-05-29T14:02:55Z","msg":"Starting EventSource","controller":"opentelemetrycollector","controllerGroup":"opentelemetry.io","controllerKind":"OpenTelemetryCollector","source":"kind source: *v1alpha1.OpenTelemetryCollector"}
{"level":"info","ts":"2024-05-29T14:02:55Z","msg":"Starting EventSource","controller":"opentelemetrycollector","controllerGroup":"opentelemetry.io","controllerKind":"OpenTelemetryCollector","source":"kind source: *v1.ConfigMap"}
{"level":"info","ts":"2024-05-29T14:02:55Z","msg":"Starting EventSource","controller":"opentelemetrycollector","controllerGroup":"opentelemetry.io","controllerKind":"OpenTelemetryCollector","source":"kind source: *v1.ServiceAccount"}
{"level":"info","ts":"2024-05-29T14:02:55Z","msg":"Starting EventSource","controller":"opentelemetrycollector","controllerGroup":"opentelemetry.io","controllerKind":"OpenTelemetryCollector","source":"kind source: *v1.Service"}
{"level":"info","ts":"2024-05-29T14:02:55Z","msg":"Starting EventSource","controller":"opentelemetrycollector","controllerGroup":"opentelemetry.io","controllerKind":"OpenTelemetryCollector","source":"kind source: *v1.Deployment"}
{"level":"info","ts":"2024-05-29T14:02:55Z","msg":"Starting EventSource","controller":"opentelemetrycollector","controllerGroup":"opentelemetry.io","controllerKind":"OpenTelemetryCollector","source":"kind source: *v1.DaemonSet"}
{"level":"info","ts":"2024-05-29T14:02:55Z","msg":"Starting EventSource","controller":"opentelemetrycollector","controllerGroup":"opentelemetry.io","controllerKind":"OpenTelemetryCollector","source":"kind source: *v1.StatefulSet"}
{"level":"info","ts":"2024-05-29T14:02:55Z","msg":"Starting EventSource","controller":"opentelemetrycollector","controllerGroup":"opentelemetry.io","controllerKind":"OpenTelemetryCollector","source":"kind source: *v2.HorizontalPodAutoscaler"}
{"level":"info","ts":"2024-05-29T14:02:55Z","msg":"Starting EventSource","controller":"opentelemetrycollector","controllerGroup":"opentelemetry.io","controllerKind":"OpenTelemetryCollector","source":"kind source: *v1.PodDisruptionBudget"}
{"level":"info","ts":"2024-05-29T14:02:55Z","msg":"Starting Controller","controller":"opentelemetrycollector","controllerGroup":"opentelemetry.io","controllerKind":"OpenTelemetryCollector"}
{"level":"info","ts":"2024-05-29T14:02:55Z","msg":"Starting EventSource","controller":"opampbridge","controllerGroup":"opentelemetry.io","controllerKind":"OpAMPBridge","source":"kind source: *v1alpha1.OpAMPBridge"}
{"level":"info","ts":"2024-05-29T14:02:55Z","msg":"Starting EventSource","controller":"opampbridge","controllerGroup":"opentelemetry.io","controllerKind":"OpAMPBridge","source":"kind source: *v1.ConfigMap"}
{"level":"info","ts":"2024-05-29T14:02:55Z","msg":"Starting EventSource","controller":"opampbridge","controllerGroup":"opentelemetry.io","controllerKind":"OpAMPBridge","source":"kind source: *v1.ServiceAccount"}
{"level":"info","ts":"2024-05-29T14:02:55Z","msg":"Starting EventSource","controller":"opampbridge","controllerGroup":"opentelemetry.io","controllerKind":"OpAMPBridge","source":"kind source: *v1.Service"}
{"level":"info","ts":"2024-05-29T14:02:55Z","msg":"Starting EventSource","controller":"opampbridge","controllerGroup":"opentelemetry.io","controllerKind":"OpAMPBridge","source":"kind source: *v1.Deployment"}
{"level":"info","ts":"2024-05-29T14:02:55Z","msg":"Starting Controller","controller":"opampbridge","controllerGroup":"opentelemetry.io","controllerKind":"OpAMPBridge"}
W0529 14:02:55.892560       1 warnings.go:70] OpenTelemetryCollector v1alpha1 is deprecated. Migrate to v1beta1.
{"level":"info","ts":"2024-05-29T14:02:55Z","logger":"instrumentation-upgrade","msg":"no instances to upgrade"}
W0529 14:02:56.096746       1 warnings.go:70] OpenTelemetryCollector v1alpha1 is deprecated. Migrate to v1beta1.
{"level":"info","ts":"2024-05-29T14:02:56Z","logger":"collector-upgrade","msg":"no instances to upgrade"}
{"level":"info","ts":"2024-05-29T14:02:57Z","msg":"Starting workers","controller":"opentelemetrycollector","controllerGroup":"opentelemetry.io","controllerKind":"OpenTelemetryCollector","worker count":1}
{"level":"info","ts":"2024-05-29T14:02:57Z","msg":"Starting workers","controller":"opampbridge","controllerGroup":"opentelemetry.io","controllerKind":"OpAMPBridge","worker count":1}

This is the only thing that look weird for me :

I0529 14:02:55.705794       1 leaderelection.go:250] attempting to acquire leader lease opentelemetry-operator-system/9f7554c3.opentelemetry.io...
W0529 14:02:55.892560       1 warnings.go:70] OpenTelemetryCollector v1alpha1 is deprecated. Migrate to v1beta1.
I0529 14:02:55.809131       1 leaderelection.go:260] successfully acquired lease opentelemetry-operator-system/9f7554c3.opentelemetry.io

And i have also see this line :

{"level":"info","ts":"2024-05-29T14:02:55Z","logger":"controller-runtime.webhook","msg":"Registering webhook","path":"/validate-opentelemetry-io-v1alpha1-opentelemetrycollector"}

Why there is v1alpha1 and not v1beta1 !?

hm... and i think you've confirmed that the request should make it all the way there (the service exists, the version is right, etc.) I'm going to attempt to repro this in my kind cluster right now. I have done a successful installation of the operator recently, but I will try once more.

okay i just attempted a fresh installation following the reproduction steps you mentioned and couldn't trigger the same error...

Commands run and outputs

```
⎨ 10:24:27⎬ ⎨ ⛵ : ⎬ ⎨ 🐍 3.10.0⎬ ⎨ ...workspace/playground/opentelemetry-helm-charts⎬ ⎨  add-presets ✔⎬
⫸ kind create cluster
Creating cluster "kind" ...
✓ Ensuring node image (kindest/node:v1.26.3) 🖼
✓ Preparing nodes 📦
✓ Writing configuration 📜
✓ Starting control-plane 🕹
✓ Installing CNI 🔌
✓ Installing StorageClass 💾
Set kubectl context to "kind-kind"
You can now use your cluster with:
kubectl cluster-info --context kind-kind
Not sure what to do next? 😅  Check out https://kind.sigs.k8s.io/docs/user/quick-start/
⎨ 10:24:46⎬ ⎨ ⛵kind-kind : kind-kind⎬ ⎨ 🐍 3.10.0⎬ ⎨ ...workspace/playground/opentelemetry-helm-charts⎬ ⎨  add-presets ✔⎬
⫸ helm install
cert-manager jetstack/cert-manager
--namespace cert-manager
--create-namespace
--version v1.14.5
--set installCRDs=true
NAME: cert-manager
LAST DEPLOYED: Wed May 29 10:25:09 2024
NAMESPACE: cert-manager
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
cert-manager v1.14.5 has been deployed successfully!
In order to begin issuing certificates, you will need to set up a ClusterIssuer
or Issuer resource (for example, by creating a 'letsencrypt-staging' issuer).
More information on the different types of issuers and how to configure them
can be found in our documentation:
https://cert-manager.io/docs/configuration/
For information on how to configure cert-manager to automatically provision
Certificates for Ingress resources, take a look at the ingress-shim
documentation:
https://cert-manager.io/docs/usage/ingress/
⎨ 10:25:28⎬ ⎨ ⛵kind-kind : kind-kind⎬ ⎨ 🐍 3.10.0⎬ ⎨ ...workspace/playground/opentelemetry-helm-charts⎬ ⎨  add-presets ✔⎬
⫸ k get pods -A
NAMESPACE            NAME                                         READY   STATUS    RESTARTS   AGE
cert-manager         cert-manager-5b68f4b794-pfxnb                1/1     Running   0          21s
cert-manager         cert-manager-cainjector-7778444ddd-xqkfn     1/1     Running   0          21s
cert-manager         cert-manager-webhook-86c74c6db8-gfbwx        1/1     Running   0          21s
kube-system          coredns-787d4945fb-2kn4x                     1/1     Running   0          34s
kube-system          coredns-787d4945fb-g6w9r                     1/1     Running   0          34s
kube-system          etcd-kind-control-plane                      1/1     Running   0          48s
kube-system          kindnet-5pwqm                                1/1     Running   0          34s
kube-system          kube-apiserver-kind-control-plane            1/1     Running   0          48s
kube-system          kube-controller-manager-kind-control-plane   1/1     Running   0          48s
kube-system          kube-proxy-bs62f                             1/1     Running   0          34s
kube-system          kube-scheduler-kind-control-plane            1/1     Running   0          48s
local-path-storage   local-path-provisioner-75f5b54ffd-hqjr4      1/1     Running   0          34s
⎨ 10:25:32⎬ ⎨ ⛵kind-kind : kind-kind⎬ ⎨ 🐍 3.10.0⎬ ⎨ ...workspace/playground/opentelemetry-helm-charts⎬ ⎨  add-presets ✔⎬
⫸ helm install opentelemetry-operator open-telemetry/opentelemetry-operator
--namespace opentelemetry-operator-system
--set "manager.collectorImage.repository=otel/opentelemetry-collector-k8s" --create-namespace
NAME: opentelemetry-operator
LAST DEPLOYED: Wed May 29 10:25:46 2024
NAMESPACE: opentelemetry-operator-system
STATUS: deployed
REVISION: 1
NOTES:
opentelemetry-operator has been installed. Check its status by running:
kubectl --namespace opentelemetry-operator-system get pods -l "release=opentelemetry-operator"
Visit https://github.com/open-telemetry/opentelemetry-operator for instructions on how to create & configure OpenTelemetryCollector and Instrumentation custom resources by using the Operator.
⎨ 10:25:47⎬ ⎨ ⛵kind-kind : kind-kind⎬ ⎨ 🐍 3.10.0⎬ ⎨ ...workspace/playground/opentelemetry-helm-charts⎬ ⎨  add-presets ✔⎬
⫸ k get pods
No resources found in default namespace.
⎨ 10:25:51⎬ ⎨ ⛵kind-kind : kind-kind⎬ ⎨ 🐍 3.10.0⎬ ⎨ ...workspace/playground/opentelemetry-helm-charts⎬ ⎨  add-presets ✔⎬
⫸ k get pods -A
NAMESPACE                       NAME                                         READY   STATUS              RESTARTS   AGE
cert-manager                    cert-manager-5b68f4b794-pfxnb                1/1     Running             0          43s
cert-manager                    cert-manager-cainjector-7778444ddd-xqkfn     1/1     Running             0          43s
cert-manager                    cert-manager-webhook-86c74c6db8-gfbwx        1/1     Running             0          43s
kube-system                     coredns-787d4945fb-2kn4x                     1/1     Running             0          56s
kube-system                     coredns-787d4945fb-g6w9r                     1/1     Running             0          56s
kube-system                     etcd-kind-control-plane                      1/1     Running             0          70s
kube-system                     kindnet-5pwqm                                1/1     Running             0          56s
kube-system                     kube-apiserver-kind-control-plane            1/1     Running             0          70s
kube-system                     kube-controller-manager-kind-control-plane   1/1     Running             0          70s
kube-system                     kube-proxy-bs62f                             1/1     Running             0          56s
kube-system                     kube-scheduler-kind-control-plane            1/1     Running             0          70s
local-path-storage              local-path-provisioner-75f5b54ffd-hqjr4      1/1     Running             0          56s
opentelemetry-operator-system   opentelemetry-operator-7cd4bb84f6-s54sc      0/2     ContainerCreating   0          6s
⎨ 10:25:53⎬ ⎨ ⛵kind-kind : kind-kind⎬ ⎨ 🐍 3.10.0⎬ ⎨ ...workspace/playground/opentelemetry-helm-charts⎬ ⎨  add-presets ✔⎬
⫸ k get pods -A
NAMESPACE                       NAME                                         READY   STATUS              RESTARTS   AGE
cert-manager                    cert-manager-5b68f4b794-pfxnb                1/1     Running             0          45s
cert-manager                    cert-manager-cainjector-7778444ddd-xqkfn     1/1     Running             0          45s
cert-manager                    cert-manager-webhook-86c74c6db8-gfbwx        1/1     Running             0          45s
kube-system                     coredns-787d4945fb-2kn4x                     1/1     Running             0          58s
kube-system                     coredns-787d4945fb-g6w9r                     1/1     Running             0          58s
kube-system                     etcd-kind-control-plane                      1/1     Running             0          72s
kube-system                     kindnet-5pwqm                                1/1     Running             0          58s
kube-system                     kube-apiserver-kind-control-plane            1/1     Running             0          72s
kube-system                     kube-controller-manager-kind-control-plane   1/1     Running             0          72s
kube-system                     kube-proxy-bs62f                             1/1     Running             0          58s
kube-system                     kube-scheduler-kind-control-plane            1/1     Running             0          72s
local-path-storage              local-path-provisioner-75f5b54ffd-hqjr4      1/1     Running             0          58s
opentelemetry-operator-system   opentelemetry-operator-7cd4bb84f6-s54sc      0/2     ContainerCreating   0          8s
⎨ 10:25:56⎬ ⎨ ⛵kind-kind : kind-kind⎬ ⎨ 🐍 3.10.0⎬ ⎨ ...workspace/playground/opentelemetry-helm-charts⎬ ⎨  add-presets ✔⎬
⫸ k get pods -A
NAMESPACE                       NAME                                         READY   STATUS              RESTARTS   AGE
cert-manager                    cert-manager-5b68f4b794-pfxnb                1/1     Running             0          47s
cert-manager                    cert-manager-cainjector-7778444ddd-xqkfn     1/1     Running             0          47s
cert-manager                    cert-manager-webhook-86c74c6db8-gfbwx        1/1     Running             0          47s
kube-system                     coredns-787d4945fb-2kn4x                     1/1     Running             0          60s
kube-system                     coredns-787d4945fb-g6w9r                     1/1     Running             0          60s
kube-system                     etcd-kind-control-plane                      1/1     Running             0          74s
kube-system                     kindnet-5pwqm                                1/1     Running             0          60s
kube-system                     kube-apiserver-kind-control-plane            1/1     Running             0          74s
kube-system                     kube-controller-manager-kind-control-plane   1/1     Running             0          74s
kube-system                     kube-proxy-bs62f                             1/1     Running             0          60s
kube-system                     kube-scheduler-kind-control-plane            1/1     Running             0          74s
local-path-storage              local-path-provisioner-75f5b54ffd-hqjr4      1/1     Running             0          60s
opentelemetry-operator-system   opentelemetry-operator-7cd4bb84f6-s54sc      0/2     ContainerCreating   0          10s
⎨ 10:25:58⎬ ⎨ ⛵kind-kind : kind-kind⎬ ⎨ 🐍 3.10.0⎬ ⎨ ...workspace/playground/opentelemetry-helm-charts⎬ ⎨  add-presets ✔⎬
⫸ k logs opentelemetry-operator-7cd4bb84f6-s54sc -f -n opentelemetry-operator-system
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","message":"Starting the OpenTelemetry Operator","opentelemetry-operator":"0.100.1","opentelemetry-collector":"otel/opentelemetry-collector-k8s:0.100.0","opentelemetry-targetallocator":"ghcr.io/open-telemetry/opentelemetry-operator/target-allocator:0.100.0","operator-opamp-bridge":"ghcr.io/open-telemetry/opentelemetry-operator/operator-opamp-bridge:0.100.0","auto-instrumentation-java":"ghcr.io/open-telemetry/opentelemetry-operator/autoinstrumentation-java:1.32.1","auto-instrumentation-nodejs":"ghcr.io/open-telemetry/opentelemetry-operator/autoinstrumentation-nodejs:0.51.0","auto-instrumentation-python":"ghcr.io/open-telemetry/opentelemetry-operator/autoinstrumentation-python:0.44b0","auto-instrumentation-dotnet":"ghcr.io/open-telemetry/opentelemetry-operator/autoinstrumentation-dotnet:1.2.0","auto-instrumentation-go":"ghcr.io/open-telemetry/opentelemetry-go-instrumentation/autoinstrumentation-go:v0.12.0-alpha","auto-instrumentation-apache-httpd":"ghcr.io/open-telemetry/opentelemetry-operator/autoinstrumentation-apache-httpd:1.0.4","auto-instrumentation-nginx":"ghcr.io/open-telemetry/opentelemetry-operator/autoinstrumentation-apache-httpd:1.0.4","feature-gates":"operator.observability.prometheus","build-date":"2024-05-20T20:42:10Z","go-version":"go1.21.10","go-arch":"arm64","go-os":"linux","labels-filter":[],"annotations-filter":[],"enable-multi-instrumentation":false,"enable-apache-httpd-instrumentation":true,"enable-dotnet-instrumentation":true,"enable-go-instrumentation":false,"enable-python-instrumentation":true,"enable-nginx-instrumentation":false,"enable-nodejs-instrumentation":true,"enable-java-instrumentation":true,"zap-message-key":"message","zap-level-key":"level","zap-time-key":"timestamp","zap-level-format":"uppercase"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","logger":"setup","message":"the env var WATCH_NAMESPACE isn't set, watching all namespaces"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","logger":"setup","message":"Prometheus CRDs are not installed, skipping adding to scheme."}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","logger":"setup","message":"Openshift CRDs are not installed, skipping adding to scheme."}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","logger":"controller-runtime.builder","message":"Registering a mutating webhook","GVK":"opentelemetry.io/v1beta1, Kind=OpenTelemetryCollector","path":"/mutate-opentelemetry-io-v1beta1-opentelemetrycollector"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","logger":"controller-runtime.webhook","message":"Registering webhook","path":"/mutate-opentelemetry-io-v1beta1-opentelemetrycollector"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","logger":"controller-runtime.builder","message":"Registering a validating webhook","GVK":"opentelemetry.io/v1beta1, Kind=OpenTelemetryCollector","path":"/validate-opentelemetry-io-v1beta1-opentelemetrycollector"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","logger":"controller-runtime.webhook","message":"Registering webhook","path":"/validate-opentelemetry-io-v1beta1-opentelemetrycollector"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","logger":"controller-runtime.webhook","message":"Registering webhook","path":"/convert"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","logger":"controller-runtime.builder","message":"Conversion webhook enabled","GVK":"opentelemetry.io/v1beta1, Kind=OpenTelemetryCollector"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","logger":"controller-runtime.builder","message":"Registering a mutating webhook","GVK":"opentelemetry.io/v1alpha1, Kind=Instrumentation","path":"/mutate-opentelemetry-io-v1alpha1-instrumentation"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","logger":"controller-runtime.webhook","message":"Registering webhook","path":"/mutate-opentelemetry-io-v1alpha1-instrumentation"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","logger":"controller-runtime.builder","message":"Registering a validating webhook","GVK":"opentelemetry.io/v1alpha1, Kind=Instrumentation","path":"/validate-opentelemetry-io-v1alpha1-instrumentation"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","logger":"controller-runtime.webhook","message":"Registering webhook","path":"/validate-opentelemetry-io-v1alpha1-instrumentation"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","logger":"controller-runtime.webhook","message":"Registering webhook","path":"/mutate-v1-pod"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","logger":"controller-runtime.builder","message":"Registering a mutating webhook","GVK":"opentelemetry.io/v1alpha1, Kind=OpAMPBridge","path":"/mutate-opentelemetry-io-v1alpha1-opampbridge"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","logger":"controller-runtime.webhook","message":"Registering webhook","path":"/mutate-opentelemetry-io-v1alpha1-opampbridge"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","logger":"controller-runtime.builder","message":"Registering a validating webhook","GVK":"opentelemetry.io/v1alpha1, Kind=OpAMPBridge","path":"/validate-opentelemetry-io-v1alpha1-opampbridge"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","logger":"controller-runtime.webhook","message":"Registering webhook","path":"/validate-opentelemetry-io-v1alpha1-opampbridge"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","logger":"setup","message":"starting manager"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","logger":"controller-runtime.metrics","message":"Starting metrics server"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","logger":"controller-runtime.metrics","message":"Serving metrics server","bindAddress":"<IP_ADDRESS>:8080","secure":false}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","message":"starting server","kind":"health probe","addr":"[::]:8081"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","logger":"controller-runtime.webhook","message":"Starting webhook server"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","logger":"controller-runtime.certwatcher","message":"Updated current TLS certificate"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","logger":"controller-runtime.webhook","message":"Serving webhook server","host":"","port":9443}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","logger":"controller-runtime.certwatcher","message":"Starting certificate watcher"}
I0529 14:25:55.782000       1 leaderelection.go:250] attempting to acquire leader lease opentelemetry-operator-system/9f7554c3.opentelemetry.io...
I0529 14:25:55.785483       1 leaderelection.go:260] successfully acquired lease opentelemetry-operator-system/9f7554c3.opentelemetry.io
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","logger":"collector-upgrade","message":"looking for managed instances to upgrade"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","message":"Starting EventSource","controller":"opentelemetrycollector","controllerGroup":"opentelemetry.io","controllerKind":"OpenTelemetryCollector","source":"kind source: *v1beta1.OpenTelemetryCollector"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","message":"Starting EventSource","controller":"opentelemetrycollector","controllerGroup":"opentelemetry.io","controllerKind":"OpenTelemetryCollector","source":"kind source: *v1.ConfigMap"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","message":"Starting EventSource","controller":"opentelemetrycollector","controllerGroup":"opentelemetry.io","controllerKind":"OpenTelemetryCollector","source":"kind source: *v1.ServiceAccount"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","message":"Starting EventSource","controller":"opentelemetrycollector","controllerGroup":"opentelemetry.io","controllerKind":"OpenTelemetryCollector","source":"kind source: *v1.Service"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","message":"Starting EventSource","controller":"opentelemetrycollector","controllerGroup":"opentelemetry.io","controllerKind":"OpenTelemetryCollector","source":"kind source: *v1.Deployment"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","message":"Starting EventSource","controller":"opentelemetrycollector","controllerGroup":"opentelemetry.io","controllerKind":"OpenTelemetryCollector","source":"kind source: *v1.DaemonSet"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","message":"Starting EventSource","controller":"opentelemetrycollector","controllerGroup":"opentelemetry.io","controllerKind":"OpenTelemetryCollector","source":"kind source: *v1.StatefulSet"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","message":"Starting EventSource","controller":"opentelemetrycollector","controllerGroup":"opentelemetry.io","controllerKind":"OpenTelemetryCollector","source":"kind source: *v1.PersistentVolume"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","message":"Starting EventSource","controller":"opentelemetrycollector","controllerGroup":"opentelemetry.io","controllerKind":"OpenTelemetryCollector","source":"kind source: *v1.PersistentVolumeClaim"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","message":"Starting EventSource","controller":"opentelemetrycollector","controllerGroup":"opentelemetry.io","controllerKind":"OpenTelemetryCollector","source":"kind source: *v1.Ingress"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","message":"Starting EventSource","controller":"opentelemetrycollector","controllerGroup":"opentelemetry.io","controllerKind":"OpenTelemetryCollector","source":"kind source: *v2.HorizontalPodAutoscaler"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","message":"Starting EventSource","controller":"opentelemetrycollector","controllerGr
oup":"opentelemetry.io","controllerKind":"OpenTelemetryCollector","source":"kind source: *v1.PodDisruptionBudget"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","message":"Starting Controller","controller":"opentelemetrycollector","controllerGroup":"opentelemetry.io","controllerKind":"OpenTelemetryCollector"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","logger":"instrumentation-upgrade","message":"looking for managed Instrumentation instances to upgrade"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","message":"Starting EventSource","controller":"opampbridge","controllerGroup":"opentelemetry.io","controllerKind":"OpAMPBridge","source":"kind source: *v1alpha1.OpAMPBridge"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","message":"Starting EventSource","controller":"opampbridge","controllerGroup":"opentelemetry.io","controllerKind":"OpAMPBridge","source":"kind source: *v1.ConfigMap"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","message":"Starting EventSource","controller":"opampbridge","controllerGroup":"opentelemetry.io","controllerKind":"OpAMPBridge","source":"kind source: *v1.ServiceAccount"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","message":"Starting EventSource","controller":"opampbridge","controllerGroup":"opentelemetry.io","controllerKind":"OpAMPBridge","source":"kind source: *v1.Service"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","message":"Starting EventSource","controller":"opampbridge","controllerGroup":"opentelemetry.io","controllerKind":"OpAMPBridge","source":"kind source: *v1.Deployment"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","message":"Starting Controller","controller":"opampbridge","controllerGroup":"opentelemetry.io","controllerKind":"OpAMPBridge"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","logger":"instrumentation-upgrade","message":"no instances to upgrade"}
{"level":"INFO","timestamp":"2024-05-29T14:25:55Z","logger":"collector-upgrade","message":"no instances to upgrade"}
{"level":"INFO","timestamp":"2024-05-29T14:25:56Z","message":"Starting workers","controller":"opampbridge","controllerGroup":"opentelemetry.io","controllerKind":"OpAMPBridge","worker count":1}
{"level":"INFO","timestamp":"2024-05-29T14:25:56Z","message":"Starting workers","controller":"opentelemetrycollector","controllerGroup":"opentelemetry.io","controllerKind":"OpenTelemetryCollector","worker count":1}
^C
⎨ ✘⎬ ⎨ 10:26:10⎬ ⎨ ⛵kind-kind : kind-kind⎬ ⎨ 🐍 3.10.0⎬ ⎨ ...workspace/playground/opentelemetry-helm-charts⎬ ⎨  add-presets ✔⎬
⫸ k get crd opentelemetrycollectors.opentelemetry.io -o yaml | grep 'conversion'
conversion:
conversionReviewVersions:
⎨ 10:26:30⎬ ⎨ ⛵kind-kind : kind-kind⎬ ⎨ 🐍 3.10.0⎬ ⎨ ...workspace/playground/opentelemetry-helm-charts⎬ ⎨  add-presets ✔⎬
⫸ vi example.yaml
⎨ 10:26:55⎬ ⎨ ⛵kind-kind : kind-kind⎬ ⎨ 🐍 3.10.0⎬ ⎨ ...workspace/playground/opentelemetry-helm-charts⎬ ⎨  add-presets ✔⎬
⫸ kubectl apply -f - <<EOF
apiVersion: opentelemetry.io/v1alpha1
kind: OpenTelemetryCollector
metadata:
name: my-collector
spec:
mode: deployment # This configuration is omittable.
config: |
receivers:
jaeger:
protocols:
grpc:
processors:
exporters:
  debug:

service:
  pipelines:
    traces:
      receivers: [jaeger]
      processors: []
      exporters: [debug]

EOF
Warning: OpenTelemetryCollector v1alpha1 is deprecated. Migrate to v1beta1.
Warning: Collector config spec.config has null objects: exporters.debug:, receivers.jaeger.protocols.grpc:. For compatibility with other tooling, such as kustomize and kubectl edit, it is recommended to use empty objects e.g. batch: {}.
opentelemetrycollector.opentelemetry.io/my-collector created
⎨ 10:27:07⎬ ⎨ ⛵kind-kind : kind-kind⎬ ⎨ 🐍 3.10.0⎬ ⎨ ...workspace/playground/opentelemetry-helm-charts⎬ ⎨  add-presets ✔⎬
⫸ k get otelcol
NAME           MODE         VERSION   READY   AGE   IMAGE                                      MANAGEMENT
my-collector   deployment   0.100.0   0/1     7s    otel/opentelemetry-collector-k8s:0.100.0   managed
</details>

if this can maybe help you :
$ k3s --version
k3s version v1.29.5+k3s1 (4e53a323)
go version go1.21.9
$ helm version
version.BuildInfo{Version:"v3.13.1", GitCommit:"3547a4b5bf5edb5478ce352e18858d8a552a4110", GitTreeState:"clean", GoVersion:"go1.20.8"}

@PandeoF1 i just created a k3s cluster (I need to use k3d.io because i'm on a mac, but it's running the same thing), following these steps and was successful.
⎨ 11:03:05⎬ ⎨ ⛵k3d-k3s-default : admin@k3d-k3s-default⎬ ⎨ 🐍 3.10.0⎬ ⎨ ...workspace/playground/opentelemetry-helm-charts⎬ ⎨  add-presets ✔⎬
⫸ k3d version
k3d version v5.6.3
k3s version v1.28.8-k3s1 (default)

⎨ 11:03:22⎬ ⎨ ⛵k3d-k3s-default : admin@k3d-k3s-default⎬ ⎨ 🐍 3.10.0⎬ ⎨ ...workspace/playground/opentelemetry-helm-charts⎬ ⎨  add-presets ✔⎬
⫸ helm version
version.BuildInfo{Version:"v3.14.3", GitCommit:"f03cc04caaa8f6d7c3e67cf918929150cf6f3f12", GitTreeState:"clean", GoVersion:"go1.21.7"}

k3d cluster create
k get pods -A
helm install \\n  cert-manager jetstack/cert-manager \\n  --namespace cert-manager \\n  --create-namespace \\n  --version v1.14.5 \\n  --set installCRDs=true
k get pods
k get pods -A
helm install opentelemetry-operator open-telemetry/opentelemetry-operator \\n--namespace opentelemetry-operator-system \\n--set "manager.collectorImage.repository=otel/opentelemetry-collector-k8s" --create-namespace
k get pods
k get pods -A
k logs opentelemetry-operator-dd66988d4-c6kb9 -f -n opentelemetry-operator-system
kubectl apply -f - <<EOF\napiVersion: opentelemetry.io/v1alpha1\nkind: OpenTelemetryCollector\nmetadata:\n  name: my-collector\nspec:\n  mode: deployment # This configuration is omittable.\n  config: |\n    receivers:\n      jaeger:\n        protocols:\n          grpc:\n    processors:\n\n    exporters:\n      debug:\n\n    service:\n      pipelines:\n        traces:\n          receivers: [jaeger]\n          processors: []\n          exporters: [debug]\nEOF
k get pods
k3d version
helm version

Did I do anything differently than what you attempted? Could you attempt these steps and let me know if you get the same issue?

Ok after a installation with a clean cluster and all of your commands it work..
The only difference from my first install is in the cert-manager
helm install
cert-manager jetstack/cert-manager
--namespace cert-manager
--create-namespace
--version v1.14.5
--set installCRDs=true <<<<<<<

IDK the installCRDs can generate my issue (i will test it tomorrow #ImFrenchSoMyDayIsFinish x) ) but it's the only thing different.
Tomorrow i will try to find how i can generate my problem to help you to solve it ! (If it's not me the problem...)

ohhhh that would make sense then – maybe you didn't install the certs so the webhook certs were failing maybe?? Either way if you can reproduce this, that would be amazing. I've seen this bug pop up everynow and then for the past few years and would love to get to the bottom of it.

I did it @jaronoff97 !!!!
I think the problem is due to a difference of version between the helm and the image used inside.
$ helm install opentelemetry-operator open-telemetry/opentelemetry-operator \
--namespace opentelemetry-operator-system \
--set "manager.collectorImage.repository=my-registry.com/open-telemetry/opentelemetry-collector" \
--set "manager.collectorImage.tag=0.98.0" \
--set "manager.image.repository=my-registry.com/open-telemetry/opentelemetry-operator" \
--set "manager.image.tag=v0.98.0" \
--set "kubeRBACProxy.image.repository=my-registry.com/brancz/kube-rbac-proxy" \
--set "kubeRBACProxy.image.tag=v0.15.0" \
--set imagePullSecrets[0].name=secret-registry

The version used by helm is the latest one (0.61.0 i think) but in my walk-trough of internal setup for our application i have set static version to 0.98.0 for the operator and collector
⫸ kind create cluster
Creating cluster "kind" ...
 ✓ Ensuring node image (kindest/node:v1.30.0) 🖼
 ✓ Preparing nodes 📦
 ✓ Writing configuration 📜
 ✓ Starting control-plane 🕹
 ✓ Installing CNI 🔌
 ✓ Installing StorageClass 💾
Set kubectl context to "kind-kind"
You can now use your cluster with:

kubectl cluster-info --context kind-kind

Not sure what to do next? 😅  Check out https://kind.sigs.k8s.io/docs/user/quick-start/

⫸ helm install \
cert-manager jetstack/cert-manager \
--namespace cert-manager \
--create-namespace \
--version v1.14.5 \
--set installCRDs=true

NAME: cert-manager
LAST DEPLOYED: Thu May 30 11:33:39 2024
NAMESPACE: cert-manager
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
cert-manager v1.14.5 has been deployed successfully!

In order to begin issuing certificates, you will need to set up a ClusterIssuer
or Issuer resource (for example, by creating a 'letsencrypt-staging' issuer).

More information on the different types of issuers and how to configure them
can be found in our documentation:

https://cert-manager.io/docs/configuration/

For information on how to configure cert-manager to automatically provision
Certificates for Ingress resources, take a look at the `ingress-shim`
documentation:

https://cert-manager.io/docs/usage/ingress/

⫸ export NAMESPACE=dev
⫸ kubectl create ns $NAMESPACE
⫸ kubectl create namespace opentelemetry-operator-system
⫸ kubectl create serviceaccount opentelemetry-operator -n $NAMESPACE
# Use the official hub.docker.com registry for your test
⫸ kubectl create secret docker-registry regcred \
--docker-server=my-registry.com \
--docker-username=xxx \
--docker-password=xxxx \
-n opentelemetry-operator-system

# Optional if hub.docker.com is used
⫸ kubectl patch serviceaccount opentelemetry-operator \
-p '{"imagePullSecrets": [{"name": "regcred"}]}' \
-n $NAMESPACE

# For this step change the registry by the official image
⫸ helm install opentelemetry-operator open-telemetry/opentelemetry-operator \
--namespace opentelemetry-operator-system \
--set "manager.collectorImage.repository=my-registry.com/open-telemetry/opentelemetry-collector" \
--set "manager.collectorImage.tag=0.98.0" \
--set "manager.image.repository=my-registry.com/open-telemetry/opentelemetry-operator" \
--set "manager.image.tag=v0.98.0" \
--set "kubeRBACProxy.image.repository=my-registry.com/brancz/kube-rbac-proxy" \
--set "kubeRBACProxy.image.tag=v0.15.0" \
--set imagePullSecrets[0].name=regcred
NAME: opentelemetry-operator
LAST DEPLOYED: Thu May 30 11:34:57 2024
NAMESPACE: opentelemetry-operator-system
STATUS: deployed
REVISION: 1
NOTES:
opentelemetry-operator has been installed. Check its status by running:
  kubectl --namespace opentelemetry-operator-system get pods -l "release=opentelemetry-operator"

Visit https://github.com/open-telemetry/opentelemetry-operator for instructions on how to create & configure OpenTelemetryCollector and Instrumentation custom resources by using the Operator.

⫸ kubectl apply -f test.yml
test.yml
apiVersion: opentelemetry.io/v1alpha1
kind: OpenTelemetryCollector
metadata:
  name: my-incredible-otel # Otel add -collector to the name
  labels:
    app.kubernetes.io/name: otel
    app.kubernetes.io/component: otel-collector
spec:
  mode: deployment
  serviceAccount: opentelemetry-operator
  config: |
    receivers:
      otlp:
        protocols:
          grpc:
            endpoint: <IP_ADDRESS>:4317
          http:
            endpoint: <IP_ADDRESS>:4318
    exporters:
      otlp:
        endpoint: x.x.x.x:5555
        tls:
          insecure: true
    processors:
      batch:
    service:
      pipelines:
        traces:
          receivers: [otlp]
          processors: [batch]
          exporters: [otlp]
        metrics:
          receivers: [otlp]
          processors: [batch]
          exporters: [otlp]
        logs:
          receivers: [otlp]
          processors: [batch]
          exporters: [otlp]

Warning: OpenTelemetryCollector v1alpha1 is deprecated. Migrate to v1beta1.
Error from server (InternalError): error when creating "test.yml": Internal error occurred: Internal error occurred: conversion webhook for opentelemetry.io/v1alpha1, Kind=OpenTelemetryCollector failed: the server could not find the requested resource
⫸ kubectl apply -f test.yaml
test.yml
apiVersion: opentelemetry.io/v1beta1
kind: OpenTelemetryCollector
metadata:
  name: my-incredible-otel # Otel add -collector to the name
  labels:
    app.kubernetes.io/name: otel
    app.kubernetes.io/component: otel-collector
spec:
  mode: deployment
  serviceAccount: opentelemetry-operator
  config:
    receivers:
      otlp:
        protocols:
          grpc:
            endpoint: <IP_ADDRESS>:4317
          http:
            endpoint: <IP_ADDRESS>:4318
    exporters:
      otlp:
        endpoint: x.x.x.x:5555
        tls:
          insecure: true
    processors:
      batch:
    service:
      pipelines:
        traces:
          receivers: [otlp]
          processors: [batch]
          exporters: [otlp]
        metrics:
          receivers: [otlp]
          processors: [batch]
          exporters: [otlp]
        logs:
          receivers: [otlp]
          processors: [batch]
          exporters: [otlp]

Error from server (InternalError): error when creating "test.yml": Internal error occurred: failed calling webhook "mopentelemetrycollectorbeta.kb.io": failed to call webhook: the server could not find the requested resource

ah yeah that would track – the old operator version wouldn't be able to pull from v1beta1. @PandeoF1 am I good to close this issue now?

ah yeah that would track – the old operator version wouldn't be able to pull from v1beta1. Thank you VERY much for your diligence here. @PandeoF1 am I good to close this issue now?

Yes it's good for me !
Thx for you help and see you ;)

I did it @jaronoff97 !!!!
I think the problem is due to a difference of version between the helm and the image used inside.
$ helm install opentelemetry-operator open-telemetry/opentelemetry-operator \
--namespace opentelemetry-operator-system \
--set "manager.collectorImage.repository=my-registry.com/open-telemetry/opentelemetry-collector" \
--set "manager.collectorImage.tag=0.98.0" \
--set "manager.image.repository=my-registry.com/open-telemetry/opentelemetry-operator" \
--set "manager.image.tag=v0.98.0" \
--set "kubeRBACProxy.image.repository=my-registry.com/brancz/kube-rbac-proxy" \
--set "kubeRBACProxy.image.tag=v0.15.0" \
--set imagePullSecrets[0].name=secret-registry

The version used by helm is the latest one (0.61.0 i think) but in my walk-trough of internal setup for our application i have set static version to 0.98.0 for the operator and collector
⫸ kind create cluster
Creating cluster "kind" ...
 ✓ Ensuring node image (kindest/node:v1.30.0) 🖼
 ✓ Preparing nodes 📦
 ✓ Writing configuration 📜
 ✓ Starting control-plane 🕹
 ✓ Installing CNI 🔌
 ✓ Installing StorageClass 💾
Set kubectl context to "kind-kind"
You can now use your cluster with:

kubectl cluster-info --context kind-kind

Not sure what to do next? 😅  Check out https://kind.sigs.k8s.io/docs/user/quick-start/

⫸ helm install \
cert-manager jetstack/cert-manager \
--namespace cert-manager \
--create-namespace \
--version v1.14.5 \
--set installCRDs=true

NAME: cert-manager
LAST DEPLOYED: Thu May 30 11:33:39 2024
NAMESPACE: cert-manager
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
cert-manager v1.14.5 has been deployed successfully!

In order to begin issuing certificates, you will need to set up a ClusterIssuer
or Issuer resource (for example, by creating a 'letsencrypt-staging' issuer).

More information on the different types of issuers and how to configure them
can be found in our documentation:

https://cert-manager.io/docs/configuration/

For information on how to configure cert-manager to automatically provision
Certificates for Ingress resources, take a look at the `ingress-shim`
documentation:

https://cert-manager.io/docs/usage/ingress/

⫸ export NAMESPACE=dev
⫸ kubectl create ns $NAMESPACE
⫸ kubectl create namespace opentelemetry-operator-system
⫸ kubectl create serviceaccount opentelemetry-operator -n $NAMESPACE
# Use the official hub.docker.com registry for your test
⫸ kubectl create secret docker-registry regcred \
--docker-server=my-registry.com \
--docker-username=xxx \
--docker-password=xxxx \
-n opentelemetry-operator-system

# Optional if hub.docker.com is used
⫸ kubectl patch serviceaccount opentelemetry-operator \
-p '{"imagePullSecrets": [{"name": "regcred"}]}' \
-n $NAMESPACE

# For this step change the registry by the official image
⫸ helm install opentelemetry-operator open-telemetry/opentelemetry-operator \
--namespace opentelemetry-operator-system \
--set "manager.collectorImage.repository=my-registry.com/open-telemetry/opentelemetry-collector" \
--set "manager.collectorImage.tag=0.98.0" \
--set "manager.image.repository=my-registry.com/open-telemetry/opentelemetry-operator" \
--set "manager.image.tag=v0.98.0" \
--set "kubeRBACProxy.image.repository=my-registry.com/brancz/kube-rbac-proxy" \
--set "kubeRBACProxy.image.tag=v0.15.0" \
--set imagePullSecrets[0].name=regcred
NAME: opentelemetry-operator
LAST DEPLOYED: Thu May 30 11:34:57 2024
NAMESPACE: opentelemetry-operator-system
STATUS: deployed
REVISION: 1
NOTES:
opentelemetry-operator has been installed. Check its status by running:
  kubectl --namespace opentelemetry-operator-system get pods -l "release=opentelemetry-operator"

Visit https://github.com/open-telemetry/opentelemetry-operator for instructions on how to create & configure OpenTelemetryCollector and Instrumentation custom resources by using the Operator.

⫸ kubectl apply -f test.yml
test.yml
apiVersion: opentelemetry.io/v1alpha1
kind: OpenTelemetryCollector
metadata:
  name: my-incredible-otel # Otel add -collector to the name
  labels:
    app.kubernetes.io/name: otel
    app.kubernetes.io/component: otel-collector
spec:
  mode: deployment
  serviceAccount: opentelemetry-operator
  config: |
    receivers:
      otlp:
        protocols:
          grpc:
            endpoint: <IP_ADDRESS>:4317
          http:
            endpoint: <IP_ADDRESS>:4318
    exporters:
      otlp:
        endpoint: x.x.x.x:5555
        tls:
          insecure: true
    processors:
      batch:
    service:
      pipelines:
        traces:
          receivers: [otlp]
          processors: [batch]
          exporters: [otlp]
        metrics:
          receivers: [otlp]
          processors: [batch]
          exporters: [otlp]
        logs:
          receivers: [otlp]
          processors: [batch]
          exporters: [otlp]

Warning: OpenTelemetryCollector v1alpha1 is deprecated. Migrate to v1beta1. Error from server (InternalError): error when creating "test.yml": Internal error occurred: Internal error occurred: conversion webhook for opentelemetry.io/v1alpha1, Kind=OpenTelemetryCollector failed: the server could not find the requested resource
⫸ kubectl apply -f test.yaml
test.yml
apiVersion: opentelemetry.io/v1beta1
kind: OpenTelemetryCollector
metadata:
  name: my-incredible-otel # Otel add -collector to the name
  labels:
    app.kubernetes.io/name: otel
    app.kubernetes.io/component: otel-collector
spec:
  mode: deployment
  serviceAccount: opentelemetry-operator
  config:
    receivers:
      otlp:
        protocols:
          grpc:
            endpoint: <IP_ADDRESS>:4317
          http:
            endpoint: <IP_ADDRESS>:4318
    exporters:
      otlp:
        endpoint: x.x.x.x:5555
        tls:
          insecure: true
    processors:
      batch:
    service:
      pipelines:
        traces:
          receivers: [otlp]
          processors: [batch]
          exporters: [otlp]
        metrics:
          receivers: [otlp]
          processors: [batch]
          exporters: [otlp]
        logs:
          receivers: [otlp]
          processors: [batch]
          exporters: [otlp]

Error from server (InternalError): error when creating "test.yml": Internal error occurred: failed calling webhook "mopentelemetrycollectorbeta.kb.io": failed to call webhook: the server could not find the requested resource
(So in my documentation of the operator deployment i have change with the new images 0.101.0 and --version 0.61.0)

Hi @PandeoF1 - I have a similar issue and would like to know , if you have solved this by ensuring that Otel-operator Appversion is higher or equal to Otel-collector ? Could you suggest which Appversion works in the below scenario.
NAME                                                    CHART VERSION   APP VERSION     DESCRIPTION
open-telemetry/opentelemetry-collector  0.106.0             0.109.0                OpenTelemetry Collector Helm chart for Kubernetes
open-telemetry/opentelemetry-operator   0.69.0             0.108.0                OpenTelemetry Operator Helm chart for Kubernetes

I did it @jaronoff97 !!!!
I think the problem is due to a difference of version between the helm and the image used inside.
$ helm install opentelemetry-operator open-telemetry/opentelemetry-operator \
--namespace opentelemetry-operator-system \
--set "manager.collectorImage.repository=my-registry.com/open-telemetry/opentelemetry-collector" \
--set "manager.collectorImage.tag=0.98.0" \
--set "manager.image.repository=my-registry.com/open-telemetry/opentelemetry-operator" \
--set "manager.image.tag=v0.98.0" \
--set "kubeRBACProxy.image.repository=my-registry.com/brancz/kube-rbac-proxy" \
--set "kubeRBACProxy.image.tag=v0.15.0" \
--set imagePullSecrets[0].name=secret-registry

The version used by helm is the latest one (0.61.0 i think) but in my walk-trough of internal setup for our application i have set static version to 0.98.0 for the operator and collector
⫸ kind create cluster
Creating cluster "kind" ...
 ✓ Ensuring node image (kindest/node:v1.30.0) 🖼
 ✓ Preparing nodes 📦
 ✓ Writing configuration 📜
 ✓ Starting control-plane 🕹
 ✓ Installing CNI 🔌
 ✓ Installing StorageClass 💾
Set kubectl context to "kind-kind"
You can now use your cluster with:

kubectl cluster-info --context kind-kind

Not sure what to do next? 😅  Check out https://kind.sigs.k8s.io/docs/user/quick-start/

⫸ helm install \
cert-manager jetstack/cert-manager \
--namespace cert-manager \
--create-namespace \
--version v1.14.5 \
--set installCRDs=true

NAME: cert-manager
LAST DEPLOYED: Thu May 30 11:33:39 2024
NAMESPACE: cert-manager
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
cert-manager v1.14.5 has been deployed successfully!

In order to begin issuing certificates, you will need to set up a ClusterIssuer
or Issuer resource (for example, by creating a 'letsencrypt-staging' issuer).

More information on the different types of issuers and how to configure them
can be found in our documentation:

https://cert-manager.io/docs/configuration/

For information on how to configure cert-manager to automatically provision
Certificates for Ingress resources, take a look at the `ingress-shim`
documentation:

https://cert-manager.io/docs/usage/ingress/

⫸ export NAMESPACE=dev
⫸ kubectl create ns $NAMESPACE
⫸ kubectl create namespace opentelemetry-operator-system
⫸ kubectl create serviceaccount opentelemetry-operator -n $NAMESPACE
# Use the official hub.docker.com registry for your test
⫸ kubectl create secret docker-registry regcred \
--docker-server=my-registry.com \
--docker-username=xxx \
--docker-password=xxxx \
-n opentelemetry-operator-system

# Optional if hub.docker.com is used
⫸ kubectl patch serviceaccount opentelemetry-operator \
-p '{"imagePullSecrets": [{"name": "regcred"}]}' \
-n $NAMESPACE

# For this step change the registry by the official image
⫸ helm install opentelemetry-operator open-telemetry/opentelemetry-operator \
--namespace opentelemetry-operator-system \
--set "manager.collectorImage.repository=my-registry.com/open-telemetry/opentelemetry-collector" \
--set "manager.collectorImage.tag=0.98.0" \
--set "manager.image.repository=my-registry.com/open-telemetry/opentelemetry-operator" \
--set "manager.image.tag=v0.98.0" \
--set "kubeRBACProxy.image.repository=my-registry.com/brancz/kube-rbac-proxy" \
--set "kubeRBACProxy.image.tag=v0.15.0" \
--set imagePullSecrets[0].name=regcred
NAME: opentelemetry-operator
LAST DEPLOYED: Thu May 30 11:34:57 2024
NAMESPACE: opentelemetry-operator-system
STATUS: deployed
REVISION: 1
NOTES:
opentelemetry-operator has been installed. Check its status by running:
  kubectl --namespace opentelemetry-operator-system get pods -l "release=opentelemetry-operator"

Visit https://github.com/open-telemetry/opentelemetry-operator for instructions on how to create & configure OpenTelemetryCollector and Instrumentation custom resources by using the Operator.

⫸ kubectl apply -f test.yml
test.yml
apiVersion: opentelemetry.io/v1alpha1
kind: OpenTelemetryCollector
metadata:
  name: my-incredible-otel # Otel add -collector to the name
  labels:
    app.kubernetes.io/name: otel
    app.kubernetes.io/component: otel-collector
spec:
  mode: deployment
  serviceAccount: opentelemetry-operator
  config: |
    receivers:
      otlp:
        protocols:
          grpc:
            endpoint: <IP_ADDRESS>:4317
          http:
            endpoint: <IP_ADDRESS>:4318
    exporters:
      otlp:
        endpoint: x.x.x.x:5555
        tls:
          insecure: true
    processors:
      batch:
    service:
      pipelines:
        traces:
          receivers: [otlp]
          processors: [batch]
          exporters: [otlp]
        metrics:
          receivers: [otlp]
          processors: [batch]
          exporters: [otlp]
        logs:
          receivers: [otlp]
          processors: [batch]
          exporters: [otlp]

Warning: OpenTelemetryCollector v1alpha1 is deprecated. Migrate to v1beta1. Error from server (InternalError): error when creating "test.yml": Internal error occurred: Internal error occurred: conversion webhook for opentelemetry.io/v1alpha1, Kind=OpenTelemetryCollector failed: the server could not find the requested resource
⫸ kubectl apply -f test.yaml
test.yml
apiVersion: opentelemetry.io/v1beta1
kind: OpenTelemetryCollector
metadata:
  name: my-incredible-otel # Otel add -collector to the name
  labels:
    app.kubernetes.io/name: otel
    app.kubernetes.io/component: otel-collector
spec:
  mode: deployment
  serviceAccount: opentelemetry-operator
  config:
    receivers:
      otlp:
        protocols:
          grpc:
            endpoint: <IP_ADDRESS>:4317
          http:
            endpoint: <IP_ADDRESS>:4318
    exporters:
      otlp:
        endpoint: x.x.x.x:5555
        tls:
          insecure: true
    processors:
      batch:
    service:
      pipelines:
        traces:
          receivers: [otlp]
          processors: [batch]
          exporters: [otlp]
        metrics:
          receivers: [otlp]
          processors: [batch]
          exporters: [otlp]
        logs:
          receivers: [otlp]
          processors: [batch]
          exporters: [otlp]

Error from server (InternalError): error when creating "test.yml": Internal error occurred: failed calling webhook "mopentelemetrycollectorbeta.kb.io": failed to call webhook: the server could not find the requested resource
(So in my documentation of the operator deployment i have change with the new images 0.101.0 and --version 0.61.0)

Hi @PandeoF1 - I have a similar issue and would like to know , if you have solved this by ensuring that Otel-operator Appversion is higher or equal to Otel-collector ? Could you suggest which Appversion works in the below scenario.
NAME                                                    CHART VERSION   APP VERSION     DESCRIPTION
open-telemetry/opentelemetry-collector  0.106.0             0.109.0                OpenTelemetry Collector Helm chart for Kubernetes
open-telemetry/opentelemetry-operator   0.69.0             0.108.0                OpenTelemetry Operator Helm chart for Kubernetes

Hey @dfi470 , yes I have patched this problem by upgrading the collector version to the same/higher version of the operator!
I can't really tell you now for your version problems because I'm actually on my phone ^^' but try to use the latest image of the operator and the latest of the collector and it should be fine I guess :)

NAME CHART VERSION APP VERSION DESCRIPTION open-telemetry/opentelemetry-collector 0.106.0 0.109.0 OpenTelemetry Collector Helm chart for Kubernetes
open-telemetry/opentelemetry-operator 0.69.0 0.108.0 OpenTelemetry Operator Helm chart for Kubernetes

Thanks a lot for your instant response :) .
Strange !!! It seems like it is looking for a service whose name is incorrect .It is looking for by default service name: otel-operator-opentelemetry-operator-webhook.otel-operator.svc:443 but the existing service name is opentelemetry-operator-webhook.opentelemetry-operator-system:443 and this got created by default.
Error from server (InternalError): error when creating "kind-otel.yaml": Internal error occurred: failed calling webhook "vopentelemetrycollectorcreateupdatebeta.kb.io": failed to call webhook: Post "https://otel-operator-opentelemetry-operator-webhook.otel-operator.svc:443/validate-opentelemetry-io-v1beta1-opentelemetrycollector?timeout=10s": service "otel-operator-opentelemetry-operator-webhook" not found
[root@gr005master01 ~]# kubectl get svc  -n opentelemetry-operator-system
NAME                             TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)             AGE
opentelemetry-operator           ClusterIP   <IP_ADDRESS>           8443/TCP,8080/TCP   7m29s
opentelemetry-operator-webhook   ClusterIP   <IP_ADDRESS>           443/TCP             7m28s

Thanks a lot for your instant response :) .
Strange !!! It seems like it is looking for a service whose name is incorrect .It is looking for by default service name: otel-operator-opentelemetry-operator-webhook.otel-operator.svc:443 but the existing service name is opentelemetry-operator-webhook.opentelemetry-operator-system:443 and this got created by default.
Error from server (InternalError): error when creating "kind-otel.yaml": Internal error occurred: failed calling webhook "vopentelemetrycollectorcreateupdatebeta.kb.io": failed to call webhook: Post "https://otel-operator-opentelemetry-operator-webhook.otel-operator.svc:443/validate-opentelemetry-io-v1beta1-opentelemetrycollector?timeout=10s": service "otel-operator-opentelemetry-operator-webhook" not found
[root@gr005master01 ~]# kubectl get svc  -n opentelemetry-operator-system
NAME                             TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)             AGE
opentelemetry-operator           ClusterIP   <IP_ADDRESS>           8443/TCP,8080/TCP   7m29s
opentelemetry-operator-webhook   ClusterIP   <IP_ADDRESS>           443/TCP             7m28s

Mmhhh like that i will tell you to uninstall the operator, destroy your namespace (if you can) and re do the installation step of the operator and the collector
(Can you provide the yaml that you try to apply I will check that tomorrow ! (France timezones hehe))

Thanks a lot for your instant response :) .
Strange !!! It seems like it is looking for a service whose name is incorrect .It is looking for by default service name: otel-operator-opentelemetry-operator-webhook.otel-operator.svc:443 but the existing service name is opentelemetry-operator-webhook.opentelemetry-operator-system:443 and this got created by default.
Error from server (InternalError): error when creating "kind-otel.yaml": Internal error occurred: failed calling webhook "vopentelemetrycollectorcreateupdatebeta.kb.io": failed to call webhook: Post "https://otel-operator-opentelemetry-operator-webhook.otel-operator.svc:443/validate-opentelemetry-io-v1beta1-opentelemetrycollector?timeout=10s": service "otel-operator-opentelemetry-operator-webhook" not found
[root@gr005master01 ~]# kubectl get svc  -n opentelemetry-operator-system
NAME                             TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)             AGE
opentelemetry-operator           ClusterIP   <IP_ADDRESS>           8443/TCP,8080/TCP   7m29s
opentelemetry-operator-webhook   ClusterIP   <IP_ADDRESS>           443/TCP             7m28s

Mmhhh like that i will tell you to uninstall the operator, destroy your namespace (if you can) and re do the installation step of the operator and the collector
(Can you provide the yaml that you try to apply I will check that tomorrow ! (France timezones hehe))

Sure thanks :)
I am using the below command to install operator.
helm install opentelemetry-operator open-telemetry/opentelemetry-operator
--namespace opentelemetry-operator-system
--set "manager.collectorImage.repository=ghcr.io/open-telemetry/opentelemetry-collector/opentelemetry-collector"
--set "manager.collectorImage.tag=0.109.0"
--set "manager.image.repository=ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator"
--set "manager.image.tag=v0.108.0"
--set manager.createRbacPermissions=false (I am doing this as i wanted to have otel collector -scrape on a specific namespace withn my cluster and i have the config ready for that )
Am i am in CET (Stockholm ) zone .

Sure thanks :)
I am using the below command to install operator.
helm install opentelemetry-operator open-telemetry/opentelemetry-operator
--namespace opentelemetry-operator-system
--set "manager.collectorImage.repository=ghcr.io/open-telemetry/opentelemetry-collector/opentelemetry-collector"
--set "manager.collectorImage.tag=0.109.0"
--set "manager.image.repository=ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator"
--set "manager.image.tag=v0.108.0"
--set manager.createRbacPermissions=false____ (I am doing this as i wanted to have otel collector -scrape on a specific namespace withn my cluster and i have the config ready for that )
Am i am in CET (Stockholm ) zone .

Mmhh try without specifying the image tag by doing something like that :

helm install opentelemetry-operator open-telemetry/opentelemetry-operator
--namespace opentelemetry-operator-system
--set "manager.collectorImage.repository=ghcr.io/open-telemetry/opentelemetry-collector/opentelemetry-collector"
--set "manager.image.repository=ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator"
--set manager.createRbacPermissions=false

So it will use the latest image tag that are provided in the default values.
And which apiVersion do you use in your deployment.yaml ?

Sure thanks :)
I am using the below command to install operator.
helm install opentelemetry-operator open-telemetry/opentelemetry-operator
--namespace opentelemetry-operator-system
--set "manager.collectorImage.repository=ghcr.io/open-telemetry/opentelemetry-collector/opentelemetry-collector"
--set "manager.collectorImage.tag=0.109.0"
--set "manager.image.repository=ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator"
--set "manager.image.tag=v0.108.0"
--set manager.createRbacPermissions=false____ (I am doing this as i wanted to have otel collector -scrape on a specific namespace withn my cluster and i have the config ready for that )
Am i am in CET (Stockholm ) zone .

Mmhh try without specifying the image tag by doing something like that :

helm install opentelemetry-operator open-telemetry/opentelemetry-operator
--namespace opentelemetry-operator-system
--set "manager.collectorImage.repository=ghcr.io/open-telemetry/opentelemetry-collector/opentelemetry-collector"
--set "manager.image.repository=ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator"
--set manager.createRbacPermissions=false

So it will use the latest image tag that are provided in the default values. And which apiVersion do you use in your deployment.yaml ?

v1beta1 while creating kind:otelcollector .

@PandeoF1  - sorry , but did you got a chance to check this .


Separate index creation options from index options

Q
A

Type
improvement

BC Break
yes

Fixed issues
#841

Summary

Dropped the dropDups option for indexes since MongoDB no longer uses it
Dropped the timeout command line option for schema commands
Added maxTimeMS and writeConcern options to schema manager
Exposed maxTimeMS as well as w, wTimeout and journal options to schema commands

Note: I extracted index equivalency checks from this PR to a separate branch and will be opening a PR for that shortly. I feel those changes warrant their own discussion.


chruby 2.1 has surprise match

Spot the mistake:
$ chruby
   ruby-1.9.3-p551
   ruby-2.0.0-p648
   ruby-2.1.10
   ruby-2.2.10
   ruby-2.3.8
   ruby-2.4.10
   ruby-2.5.8
   ruby-2.6.6
   ruby-2.7.1
$ chruby 2.1
$ chruby
   ruby-1.9.3-p551
   ruby-2.0.0-p648
   ruby-2.1.10
 * ruby-2.2.10
   ruby-2.3.8
   ruby-2.4.10
   ruby-2.5.8
   ruby-2.6.6
   ruby-2.7.1

The match is fairly naive, so to discriminate, one has to write either 2.1. or ruby-2.1 (both being incompatible with rbenv, which is sadly what may end up in .ruby-version)

This looks like a duplicate of #291


provide UI for package/module loading in each language

Many of the languages in Beaker have package managers.  Our language manager should provide a UI for each of them.  Especially JavaScript.
This gives us a way to force or check the required packages that we now just depend on users to install manually.
And for JS, a UI for specifying URLs and/or bower queries that does not require the define=undefined hack.  This was the starting point for this Issue https://github.com/twosigma/beaker-notebook/issues/429

might be useful for JS: https://github.com/systemjs/systemjs

JS is now done: https://github.com/twosigma/beaker-notebook/pull/4038


Fix gobject-introspection, and package gnome-builder and dependencies

Motivation for this change
I wanted to package GNOME Builder, but to do so I first had to package two other gnome.org libraries, and then I had to fix what appears to be a bug in the Nix packaging for gobject-introspection. That bug is described in the commit message in the first commit in this series, so here I'll focus on details about the series as a whole.
I've based this series against staging, because gobject-introspection has a lot of reverse dependencies.  Implicitly, I've tested 33 packages that depend on gobject-introspection that are in the transitive closure of GNOME Builder, and they work correctly with this commit. The existing packages apparently worked correctly without this fix as well, but GNOME Builder in particular installs its libide-1.0.so in an unusual path that g-ir-scanner couldn't previously parse from ldd output.
The three new packages don't need to be built against staging, but they aren't useful without the whole series, so I figure they should all get build-tested at once.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

$ less $(nix-build -A atk.dev)/share/gir-1.0/Atk-1.0.gir | grep shared
             shared-library="libatk-1.0.so.0"

Does not look working to me. We want absolute paths.


Query about deep require

I have asked an SO question for the same - may be someone here can help.
About the note at the start of this section -

Note: If you don't want the ReactART based components and it's dependencies, do a deep require instead: import ProgressBar from 'react-native-progress/Bar';.

Based on my knowledge - without adding/configuring Webpack 2 with tree-shaking and enabling uglify by oneself - the RN bundler would not be tree shaking and removing unused modules.
Given that, would deep requiring like suggested really lead to other dependencies not being included in the final bundle?

Because the Metro bundler doesn't tree shake currently AFAIK, you would need to do a deep require to not get redundant code.

Just to confirm, do you mean 'deep requiring' would help eliminate redundant code from the final bundle or it would not(since the Metro bundler doesn't tree shake right now)?
In other words, without tree shaking - would the bundler understand that since it's a deep require, the parts that are not required should not be in the final bundle? npm install would get the full package into node_modules, irrespective of deep requires.

It would install, but won't end up in the final bundle.


Company Page - Contract View - Checked Contract Filter Required

User wants to see which Company Contract view need Checking
Solution
Add Contract checked "Is Checked" Filter for Contract View only
This should not come to Other Views
Initiated by @vinpahilwani
Verified by @mitulpanch

@vinpahilwani
Please Provide Title for "Is Checked" Filter Title

contractchecked new parameter into API for this
If Yes => Both Schedule Billing and Per-Project Billing contract is Approved
else NO => Any of Schedule OR Per-Project Contract is not Approved

Check Box Not Possible

https://www.berrycast.com/conversations/c9e631bb-8652-5d27-bd15-ad60af94f82e


static ip set in wifi- station mode in esp32 (IDFGH-3274)

hai ,
In my application i need to connect with the static IP given.
i can able to connect when used
ESP_ERROR_CHECK(tcpip_adapter_get_ip_info(TCPIP_ADAPTER_IF_STA, &ip_info);
it can able get ip with dynamic and connect with wifi
then i tried with static,
tcpip_adapter_init();
tcpip_adapter_dhcpc_stop(TCPIP_ADAPTER_IF_STA); // Don't run a DHCP client
tcpip_adapter_ip_info_t ip_info;
ip_info.ip.addr = ipaddr_addr("<IP_ADDRESS>");
ip_info.gw.addr = ipaddr_addr("<IP_ADDRESS>");
ip_info.netmask.addr = ipaddr_addr("<IP_ADDRESS>");
tcpip_adapter_set_ip_info(TCPIP_ADAPTER_IF_STA, &ip_info);
printf("IP Address:  %s\n", ip4addr_ntoa(&ip_info.ip));
printf("Subnet mask: %s\n", ip4addr_ntoa(&ip_info.netmask));
printf("Gateway:     %s\n", ip4addr_ntoa(&ip_info.gw));
ESP_ERROR_CHECK(tcpip_adapter_dhcpc_start(TCPIP_ADAPTER_IF_STA));
but always i am getting invalid static ip ...
could you please tell me on how to fix the static ip and to connect with wifi??

Hi @sowmimalu
No need to start the DHCP client after setting the address.
tcpip_adapter_set_ip_info(WIFI_IF_STA, &ip);

This should be enough to setup static IP address, after that an IP event should be received (depending on your event registration, e.g. ip_sta_got_ip_handler() if you register that function for the IP_EVENT base with the IP_EVENT_STA_GOT_IP event id)

tried now its  working...thank you

This should be closed. @Alvin1Zhang

Thanks for the notes @AxelLin . @sowmimalu Glad that it is working, feel free to reopen if the issue still happens.


Where can I find pre-trained backbone weights for initializing Yolox-nano?

According to this issue, the yolox-nano training is using pre-trained backbone on ImageNet. I was wondering where can we find the pre-trained backbone weights and use it to initialize the model? Thanks!

In the newest version, the pre-trained model is removed and you could train from scarach now.


Separate IiifPrint to its own repo

Summary
It's far to easy to accidentally submit PRs against the Newspaper Gem. We need to break the fork so that by default, PRs get submitted to IiifPrint repo.
Acceptance Criteria

[ ] PRs get merged into IiifPrint repo by default.

Screenshots or Video

Testing Instructions
Notes
https://github.com/community/community/discussions/11729#discussioncomment-4403106

ref slack convo: https://assaydepot.slack.com/archives/G0313NK5NMA/p1674747887906319

https://assaydepot.slack.com/archives/G0313NKG2DA/p1674760107849459


[AIFR] - Adding field aifRecipient to AFF for AIFR

Short explanation of the background:
During our tests, we discovered the need for an additional field in the AIFR, specifically the AIF Recipient.
It must be possible to assign the same AIF recipient to different namespaces.
The object name is derived from the namespace and the AIF Recipient. To ensure accurate derivation, we include both fields in the creation wizard and set the object name as read-only.
Since the exact derivation from object name Recipient back to Namespace and AIF Recipient may not always be possible, we displayed both fields as read-only in the editor for informational purposes.

Technically, adding new mandatory fields is considered as an incompatible change.
However, since AIFR is still in development, I think we can still accept incompatible changes. This means, we need to ignore the failing compatibility check in this PR.

We have skipped the compatibility check. See my comment above

However, since AIFR is still in development, I think we can still accept incompatible changes. This means, we need to ignore the failing compatibility check in this PR.


mwc-formfield isnt distributing mwc-formfield-css.js on NPM

Thus, isn't working

Should be fixed with 0.2.1, sorry!


fix: duplicate key "locale" in renderer.ts

duplicate key "locale" in renderer.ts

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.iqinning seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

PR 麻烦指向 develop 分支
似乎没看到有 duplication

PR 麻烦指向 develop 分支
已改


error display

extend bottom bar with repl text entry across entire window. use the additional space to display error messages

closed as duplicate of #7


I'm getting an error when I'm trying to apply to patch:

Please first read CONTRIBUTING_AND_ISSUE_TEMPLATE.md and do some research about your device!
I will close your issue without answering if you don't provide me enough information about...

Xiaomi Mi A1_tissot, kernel 3.18.71, Lineage OS 15.1
I'm getting this error patch: **** strip count ../kernel_3.18.patch is not a number
When I'm trying to patch using patch -p ../kernel_3.18.patch
what exactly you would like to have / do. Give kernel support for USB Keyboard

Fixed it but every time I make the command I get an empty output

You have to write a number after the "p", not the file name. The number specifies how "flexible" the file should be patched.

You have to write patch -p3 ../kernel_3.18.patch
Can this issue get closed?


Example: Kernel-Suite-Downgrade fails

After spending hours closing the gaps in the documentation and fixing syntax errors in some of the code (as a non-Python expert), am getting this result:
C:\Temp\WindowsDowndate>python windows_downdate.py --config-xml examples/Kernel-Suite-Downgrade/Config.xml
[INFO] Starting Windows-Downdate
Traceback (most recent call last):
  File "C:\Temp\WindowsDowndate\windows_downdate.py", line 327, in <module>
    main()
  File "C:\Temp\WindowsDowndate\windows_downdate.py", line 306, in main
    update_files = parse_config_xml(args.config_xml)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Temp\WindowsDowndate\windows_downdate.py", line 222, in parse_config_xml
    update_file_obj = UpdateFile(source_file, destination_file)
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Temp\WindowsDowndate\windows_downdate.py", line 39, in __init__
    self._source_path_obj = PathEx(source_path)
                            ^^^^^^^^^^^^^^^^^^^
  File "C:\Temp\WindowsDowndate\windows_downdate\filesystem_utils.py", line 25, in __new__
    self = cls._from_parts(args)
           ^^^^^^^^^^^^^^^
AttributeError: type object 'PathEx' has no attribute '_from_parts'. Did you mean: '_load_parts'?

I'm happy to be wrong about something in my Python setup - but this looks more like a code problem.
The Config.xml is unmodified.
PS. All other examples also fail with similar errors.

I could not repro this, but just pushed installation fixes. Make sure you pull from main and then follow installation steps. In addition, when using examples make sure you target the correct Windows version as listed in the example's readme.
I will be closing this issue for now, feel free to re-open if you encounter issues.

DID you ever fix this @GeldHades27355

Make sure you pull from main and then follow installation steps. In addition, when using examples make sure you target the correct Windows version as listed in the example's readme.
I will be closing this issue for now, feel free to re


Merging openapi from Gornoka and felixmhofmann

Resolving the clusterfuck that happened here.
@Gornoka originally pushed his fix of the openapi specification into the 336 branch on unitedmanufacturinghub repo. @felixmhofmann forked it and did additional changes. Now we are moving everything back and into staging.

Not able to resolve clusterfuck, Copying files now manually, lol


MINOR: add UPGRADE_FROM to 2.0 config docs

This config was introduced in 2.0, so we should merge this PR first and cherry-pick back to 2.0 before merging the 2.4 update

@guozhangwang @mjsax @bbejeck @vvcephei

Closing to retarget against 2.3: https://github.com/apache/kafka/pull/7831


Windows chef-client silently ignores client.rb with UTF-16 encoding

While writing a bootstrap script for chef in powershell on windows, I encountered an issue where chef-client silently ignores all settings in the client.rb file (with no errors even in debug) if the file is UTF-16 encoded (which is the default encoding for powershell's 'Out-File').
I've reproduced this on Chef versions 12.4.1 and 12.4.2 on Windows, though it may affect other versions and platforms.
To reproduce, write a client.rb file in powershell as follows:
PS C:\chef> @"
  raise 'foo'
"@ | Out-File C:\chef\client.rb

Then chef-client -c c:\chef\client.rb, chef will not raise the exception or show any warning message on its failure to load the file.
Running C:\opscode\chef\embedded\bin\file.exe C:\chef\client.rb describes the file as 'Little-endian UTF-16'
Running:
PS C:\chef> @"
  raise 'foo'
"@ | Out-File -Encoding UTF8 C:\chef\client.rb

Then chef-client -c c:\chef\client.rb will correctly raise 'foo', and 'file.exe' describes the file as 'UTF-8'.
Chef should warn the user when it cannot load its configuration due to encoding errors, or be able to load UTF-16 configuration.

Your example is both a good example and indicates it is likely not very fixable.  The workaround is to use a magic comment at the start of the file to indicate that the file is UTF-16:
# Encoding: UTF-16
raise 'foo'

Then ruby will know its UTF-16 and open it correctly.