operator-sdk
Here are 108 public repositories matching this topic...
-
Updated
Jun 27, 2021 - Go
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.
Hi, we are using our kustomize, which needs to read environment variables in the argocd-repo-server container. Can you add the ability to define variables like we did in a non-operator setup?
apiVersion: apps/v1
kind: Deployment
metadata:
name: argocd-repo-server
namespace: argocd
spec:
replicas: 5
template:
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
-
Updated
Aug 5, 2021 - Go
-
Updated
Jun 12, 2020 - Go
-
Updated
Aug 24, 2021 - Makefile
-
Updated
Jul 11, 2020 - Dockerfile
-
Updated
Dec 3, 2020 - Go
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
-
Updated
Aug 27, 2021 - Go
-
Updated
Jun 14, 2020 - Go
-
Updated
Aug 25, 2021 - Go
It should be somewhat easy to translate from reading .circleci/config.yaml
-
Updated
Jan 11, 2021 - Go
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
-
Updated
Apr 14, 2021 - Go
-
Updated
Jan 26, 2021 - Go
-
Updated
Oct 16, 2020 - HTML
-
Updated
Feb 11, 2021 - Go
-
Updated
May 26, 2020 - Go
-
Updated
May 19, 2021 - Go
-
Updated
Oct 16, 2020 - Dockerfile
-
Updated
Aug 26, 2021 - Jinja
-
Updated
Dec 13, 2018 - Go
-
Updated
Jun 8, 2020 - Dockerfile
Improve this page
Add a description, image, and links to the operator-sdk topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the operator-sdk topic, visit your repo's landing page and select "manage topics."


