k3s

This feature enables the ipsec backend for Flannel in the k3sup install command

Expected Behaviour

An additional flag to k3sup install should enable ipsec for Flannel as

Scope of your request

Do you need...

• a new flag for a command (e.g. k3d cluster create --<your-flag>)?
  • command: delete
  • flag: config

Describe the solution you'd like

Support deleting a cluster that is defined in a config file.

Describe alternatives you've considered

Parse the config file to get the cluster name.

Expected Behaviour

When using K8s 1.22 and newer, use the new namespace for ingress, for older use the deprecated API (apiVersion: extensions/v1beta1)

Several apps gener

Add events and logs in key places during service processing, such as allocate and release EIP, GoBGP synchronization Nexthop, Layer2 mode selection Node

Some clusters can be stopped when k3x is started. Users could think the current cluster should be ready, but they would really need to "start" it. We should show a warning saying something like "the current cluster is stopped".

• openfaas (serverless)
• kafka (streaming)
• postgres
• mysql
• wordpress
• spring framework
• vapor
• ruby on rails
• mongodb
• elasticsearch
• CI pipeline
• Hosted Jira
• mail server
• DNS server