kubernetes-operator

Describe the issue

Currently we run the Linter CI for golang repos using the golang-ci-linter binary. But according to the documentation it is faster and better to use the github action.
https://golangci-lint.run/usage/install/

The UX of all the error highlighting is also better.

What if we do not do this?

Finding linter errors is troublesome as users have to parse through the cons

monitored configMaps too.

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

Feature Request

Is your feature request related to a problem? Please describe.
As a user, I would like to try out the OLM tool and later would like to clean it up.

Describe the solution you'd like
Currently, I see that there is an install.sh that will install the OLM. Recirocatively, there should be an uninstall.sh.

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

For now, under "podSpec" - there is no way to set resources limits and requests for pt-heartbeat container from mysqlcluster's statefulset.

Please add option for pt-heartbeat like mysqlOperatorSidecarResources and metricsExporterResources.

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

When running kubectl schemahero install --yaml the Statefulset for the manager includes an "availableReplicas" field. This should not be present b/c it's not installable with it.

We have to update the release-drafter template to include a new section for breaking changes that is prominently shown and highlighted at the very top of the release notes. This is done to implement ADR-0011.

Most of the current use cases, automated tests and functional test scenarios were performed in context of 2 clusters only as it is most common and easier to test setup.

Meanwhile we need to be ready and test for >2 scenario cluster scenario.

This series of testing can reveal potential edge cases in current LB strategies implementation and can lead to LB logic extension and handling of >2 num

Hello,

I am trying to deploy opentelemetry-operator in GKE Autopilot (v1.21) and I am finding a weird behavior when I create a collector, the control-plane operator seems to start to create new replicaSets out of control.

1. First I installed the latest cert-manager
2. Enable firewall in GKE
3. Installed the latest release of opentelemetry-operator
4. Created a collector.

I noticed t

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