operator-sdk

Currently, the server can't connect to MongoDB with TLS mode.

Solution:

1. We need an env to take the certificate as a configmap
2. Modify the mongodb connection to add the TLS connection code.

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.
On the page https://argocd-operator.readthedocs.io/en/latest/usage/basics/#secrets it is stated:

There is a Secret that is used by Argo CD named argocd-secret. The argocd-server component reads this secret to obtain the admin password for authentication.
This Secret is managed by the operator and should not be changed direct

Is your feature request related to a problem? Please describe.
The following error shows up in the log when the GitHub webhook is tested:

{"level":"error","ts":1593630175.1589122,"logger":"handler","msg":"could not parse webhook","error":"unknown X-Github-Event in message: ","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/home/travis/gopath/pkg/mod/github.com/go-logr/zapr@v

See: https://github.com/TykTechnologies/tyk-operator/blob/master/docs/api_definitions.md#endpoint-level

Tyk Operator currently does not support allow, block & ignore list Endpoint level middlewares. (nee BlackList, WhiteList, Igno

It should be somewhat easy to translate from reading .circleci/config.yaml

In #48 there was someone that gave POSTGRES_CLOUD_PROVIDER the value AZURE while it should be Azure. This shouldn't matter and we should run the provided value through ToLower() before we make the comparison.

Description of Issue

After go-config v0.7.0, our operator breaks on startup citing that there is no provider configured.

How to Reproduce

Update the following constraint in Gopkg.toml from 0.7.0 to any later release:

[[constraint]]
  name = "github.com/micro/go-config"
  version = "0.7.0"

Install dependencies and start operat