kubernetes-cluster

Expected Behaviour

Change the default cron spec in --etcd-snapshot-schedule-cron (default: "0 */12 * * *"):

--k3s-extra-args '--etcd-snapshot-schedule-cron * * * * *'

I'm trying to apply node labels using the following configuration:

  - name: test
    instanceType: m5.large
    minSize: 1
    maxSize: 2
    desiredCapacity: 2
    labels:
      role: test
      node-role.kubernetes.io/test: ok

According to #580 and #582 using node-role subdomain should the way to apply labels, however I still get a domain error:

AWS::EKS::No

Describe the solution you'd like
When adding a configmap via the config-map field in a plugin, if we see they are adding a yaml file, why not parse it and try and see if its valid yaml? Especially with the whitespace of nesting it this can cause issues and I've hit the problem more than once.

I assume we could do a basic json/yaml validation, more if others request it.

**Anything el

At the moment of writing this issue, kubectl trace only supports X86-64 as target architecture.

The tool should be able to schedule bpftrace programs against all the architectures supported by bpftrace, that are X86-64 and arm64 (aarch64) see the Cmake definition.

To achieve that we n

What would you like to be added:
Cilium is our default CNI solution on EKS-A clusters. It would be beneficial to enable Cilium metrics so that existing Prometheus could be configured to scrape those targets.

Users that download the windows EXE will be prompted (by browser and OS) that it is not safe because the EXE isn't signed.

There is a GitHub Action for signing: https://github.com/marketplace/actions/code-sign-a-file-with-pfx-certificate

This would provide additional confidence for

Proposed change

I'd like to see our autohttps deployment be able to provide metrics that prometheus can scrape.

Who would use this feature?

Users of the helm chart that wants to ensure they don't bottleneck because low resources on this proxy pod.

(Optional): Suggest a solution

I suggest we experiment with [this Traefik configuration](https://docs.traefik.io/observability/metr

Your current KubeKey version

2.0.0

Describe this feature

OpenELB is an open-source load balancer implementation designed for exposing the LoadBalancer type of Kubernetes services in on-premises environments, it can help KubeSphere users to easily resolve this issue.

My expectation:

Make OpenELB work like Cloud Controller Manager, it can automatically assign EIP to the K8s services

Add a prometheus exporter! Example outputs:

• Layer 2
• Layer 3
• TCP LoadBalancer
• IPVS LoadBalancer (once @yastij implements it ;)
• Control Pane HA