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

I am seeing the issue with CW logstreams not getting created when using the "mounted-file" to ingest the logs from file in the container.
I picked the sample config from examples folder and able to reproduce it , below is the demo config what I have used.

apiVersion: apps/v1
kind: Deployment
metadata:
name: nginx-deployment
namespace: default
spec:
selector:
matchLabels:

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

Describe the bug
Currently we check our code with golangci-lint, which in itself catches most of the things, but having comments over exported function is not caught by it, it'll be nice to enable both the linters. Currently there are some warnings by this linter on the main branch

To Reproduce
Run: golint ./... | grep -v zz_generated #to ignore the auto-generated files

**Expe