kubernetes-operator

Describe the bug
````Warning: rbac.authorization.k8s.io/v1beta1 ClusterRoleBinding is deprecated in v1.17+, unavailable in v1.22+; use rbac.authorization.k8s.io/v1 ClusterRoleBinding``` is pointed out when running instructions found https://docs.flyte.org/en/latest/deployment/sandbox.html due to version of K8s cluster

Expected behavior
Current version of K8s is 1.21 -- we should upgra

monitored configMaps too.

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

Bug Report

What did you do?

$ git clone https://github.com/operator-framework/operator-lifecycle-manager.git
$ cd operator-lifecycle-manager
$ git describe 
v0.18.2-18-g20ded32d
$ ./scripts/install.sh v0.18.2

What did you expect to see?

The script ./scripts/install.sh v0.18.2 should return success code.

**What did you see instead? Under which circumstances

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

All the documentation on use-cases is referencing to the v1alpha1 API version, we should update to v1beta1 along with new features implemented.

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