kubernetes-operator

Describe the Issue
Currently, in flyteadmin, We are using the kind cluster for running integration tests, In that case, we need to maintain kind.

What if we do not do this?
Need to maintain kind as dependency

Related component
flyteadmin

monitored configMaps too.

`{
"configVersion":"v1",
"kubernetes":[
{
"apiVersion": "events.k8s.io/v1beta1",
"kind": "Event",
"namespace": {
"nameSelector": {
"matchNames": ["example-monitor-events"]
}
},
"fieldSelector": {
"matchExpressions": [
{
"field": "metadata.namespace",

Almost all CRD declared in operator lifecyle manager are in v1alpha1 version.
Until now it's enough but when it'll be migrated to v1, the conditions will have to respect conventions describe here:
https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#typical-status-properties

This should be put in the backlog.

The current conditions are

What would you like to be added:
Currently, kubectl kudo version only prints the current version of the KUDO CLI. It should also print the version of the KUDO controller if the con

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

Currently, we have a simple approach where the operator simply watches the namespace it was created in. But in larger env, multi-namespaces are common. To create mysql cluster in any namespace, we broadly have two approaches (1) Make mysql-operator watch and create mysql clusters in any namespace (2) Continue with current model.
However, current approach is problematic when multiple namespaces ar

Related question GoogleCloudPlatform/flink-on-k8s-operator#114

Currently, SchemaHero assumes that every Postgres table will be deployed to the public schema. It should be possible to specify the schema when defining a table

🚓 New Scanner implementation request

Add example manifests for different persistence options (EBS volume / SSD mount / RAM disk)

Currently the env variables injected are specific to this docker image https://github.com/barney-s/docker-airflow

Align it with https://github.com/puckel/docker-airflow and make necessary changes in the operator to make it work with both.

related to GoogleCloudPlatform/airflow-operator#10

This would allow in the use case where you may have more than 1 DNS server to query (for redundancy)

edgeDNSServer: &edgeDNSServer:
  - 1.1.1.1
  - 2.2.2.2 

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