Question: Must aws-observability Namespace have `aws-observability: enabled` label ?

[mikutas]

https://github.com/awsdocs/amazon-eks-user-guide/blob/master/doc_source/fargate-logging.md#log-router-configuration

kind: Namespace
apiVersion: v1
metadata:
  name: aws-observability
  labels:
    aws-observability: enabled # <- this label

[pgasca]

@mikutas, that label is required so I've updated the guide to specify that. Here's some more detail from our EKS team: "For Fargate-logging, the namespace needs to have label aws-observability: enabled for the fargate-mutation-webhook to intercept the objects specified for the namespace (configmap).
We have a namespaceselector on our webhook that matches the label- eks-fargate-mutation-webhook.yaml
If the label is removed then our webhook wont validate the confimap but our scheduler will in this case errors in validation are surfaced as events. To fail fast (while applying the configmap) we need the configmaps to be intercepted and validated by our webhook."

[mikutas]

Thank you for clarifying !

[Dpkbhatt052]

Hi ...
Is it necessary to create namespace aws-observability ?
Cant we use any other namespace for fluent bit and if yes why ?
Same I want to ask for amazon-cloudwatch namespace for logging in managed nodegroup. Is it necessary to have these namespace or we can create with any name ?