operators

Problem

K8s-event posting can fail to post an event (kind: Event) for any reasons, such as API rate limiting, temporary API failures (HTTP 5xx), control plane connectivity issues, SSL handshake failures, etc.

This leads to the events being lost, while they can represent some value. This applies both to the events created from the per-object logger messages (logger.info(...) from the

I'm not sure right now how to specify NodePort with AWX operator. Its not mentioned in documentation.

spec:
tower_ingress_type: NodePort

Ok, but how to avoid random port assignment,

Usually I can do in service deployment something like:

spec:
  type: NodePort
  ports:
    - port: 80
      nodePort: 30080
      name: http
    - port: 443
      nodePort: 30443
      name

The kuttl cli overrides the testsuite file... with the exception of the test env. (this is a require to fix that).

If the kuttl-test.yaml has a configuration for startControlPlane: true and the cli is started with --start-kind.... the cli override should start kind.

Perhaps we should have an override that allows to point at a cluster (currently it is the default that is selected if no

Is your feature request related to a problem? Please describe.

We remove the splunk plugin support because we got issues. Now there is a new version who fix that.
splunk/fluent-plugin-splunk-hec#208

Describe the solution you'd like

Re-add the splunk plugin again

PR for remove the plugin: vmware/kube-fluentd-operator#274

Descri

Describe the bug
The created ingress resource is annotated with: "kubernetes.io/ingress.class: nginx".
I use traefik, not nginx. The nexus-operator is unusable with a non-nginx ingress.

To Reproduce
Steps to reproduce the behavior:

1. Create an nexus instance with networking.exposeAs: Ingress
2. See that the ingress is created with a annotation: "kubernetes.io/ingress.class: nginx"

Please describe the problem you have
With #382, namespaced-scoped operands, i.e. Envoy DaemonSet, reside in the same namespace as the Contour. This allows using an OwnerReference instead of labels for managing the Contour<>operand relationship. The current CONTOUR_NS/CONTOUR_NAME label-based approach should be