v0.90.0 update of opentelemetry-operator

[lisguo]

Description of changes:
Pulls in all changes from v0.90.0 of the upstream opentelemetry-operator code. This is based off of of the upstream branch, with the amazon-cloudwatch-agent-operator/main branch merged on top.

New changes:

• /pkg/collector was moved to /internal/manifests/collector
• add support for apachehttpd, dotnet, golang, nginx, nodejs, python (but would still need to be enabled via ACWA CR)
• add support for healthchecks (still needs some steps for enablement)
• add support for watching statefulsets, horizontalpodautoscaler,poddisruptionbudget

		Owns(&corev1.ConfigMap{}).
		Owns(&corev1.ServiceAccount{}).
		Owns(&corev1.Service{}).
		Owns(&appsv1.Deployment{}).
		Owns(&appsv1.DaemonSet{}).
		Owns(&appsv1.StatefulSet{})

FYI the above change requires changes to the clusterrole to list the new resources. This is reflected in config/rbac but needs to be added to the helm chart.

• all unit tests were migrated from upstream (still needs some work to run)

Renamed the following:

• opentelemetry-operator -> amazon-cloudwatch-agent-operator
• OpenTelemetryCollector -> AmazonCloudWatchAgent
• opentelemetry.io -> cloudwatch.aws.amazon.com

Things that were unchanged:

• versions.txt
• ecr repo for the agent and adot instrumentation are still hardcoded in main.go
• default instrumentation logic in podmutator.go
• everything in /config, /helm, /integration-tests, /.github

As part of this upgrade, there was a commit made to migrate the securityContext from the app container to the init container. This however caused issues when I tried to use the sample app in the appsignals-demo. Potentially related to this issue. To resolve this I commented out the following line in pkg/instrumentation/sdk.go

pod = i.setInitContainerSecurityContext(pod, pod.Spec.Containers[index].SecurityContext, javaInitContainerName)

Testing
I deployed the operator, crds, and clusterroles to my EKS cluster using make deploy. I deployed the sample app in the application-signals-demo. I verified that the java instrumentation sdk is injected:

Init Containers:
  opentelemetry-auto-instrumentation-java:
    Container ID:  containerd://31a8b52c6371918bb3af4db57623e5eadc1f5c8a301b193353b27b95313499f0
    Image:         public.ecr.aws/aws-observability/adot-autoinstrumentation-java:v1.31.1
    Image ID:      public.ecr.aws/aws-observability/adot-autoinstrumentation-java@sha256:08d05d413361ea2a11e27b4392f6fe856e384136e8d28f995cfc98438aa8a3f2
    Port:          <none>
    Host Port:     <none>
    Command:
      cp
      /javaagent.jar
      /otel-auto-instrumentation-java/javaagent.jar
    State:          Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Tue, 09 Jan 2024 23:00:17 -0500
      Finished:     Tue, 09 Jan 2024 23:00:17 -0500
    Ready:          True
    Restart Count:  0
    Environment:    <none>
    Mounts:
      /otel-auto-instrumentation-java from opentelemetry-auto-instrumentation-java (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-rkqx7 (ro)

I also applied the AmazonCloudWatchAgent resource and saw the agent running

amazon-cloudwatch   cloudwatch-agent-47dph                          1/1     Running   0              12m
amazon-cloudwatch   cloudwatch-agent-zv9pf                          1/1     Running   0              12m

logs:

2024-01-10T04:48:16Z I! {"caller":"[email protected]/otlp.go:83","msg":"Starting GRPC server","kind":"receiver","name":"otlp/app_signals","data_type":"metrics","endpoint":"0.0.0.0:4315"}
2024-01-10T04:48:16Z W! {"caller":"[email protected]/warning.go:40","msg":"Using the 0.0.0.0 address exposes this server to every network interface, which may facilitate Denial of Service attacks","kind":"receiver","name":"otlp/app_signals","data_type":"metrics","documentation":"https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/security-best-practices.md#safeguards-against-denial-of-service-attacks"}
2024-01-10T04:48:16Z I! {"caller":"[email protected]/otlp.go:101","msg":"Starting HTTP server","kind":"receiver","name":"otlp/app_signals","data_type":"metrics","endpoint":"0.0.0.0:4316"}
2024-01-10T04:48:16Z I! {"caller":"service/service.go:161","msg":"Everything is ready. Begin running and processing data."}

services:

cloudwatch-agent              ClusterIP   10.100.22.172    <none>        4315/TCP,4316/TCP,2000/TCP   57m
cloudwatch-agent-headless     ClusterIP   None             <none>        4315/TCP,4316/TCP,2000/TCP   57m

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.