Expose options for k3k nodes

[galal-hussein]

There are multiple options that should be supported for exposing the clusters including:

- in-cluster service (enabled by default)
- loadbalancer service (enabled via expose.loadbalancer.enabled)

apiVersion: k3k.io/v1alpha1
kind: Cluster
metadata:
  name: loadbalancer-example
  namespace: default
spec:
  servers: 2
  agents: 3
  token: test
  version: v1.26.0-k3s2
  expose:
    loadbalancer:
      enabled: true

- ingress

apiVersion: k3k.io/v1alpha1
kind: Cluster
metadata:
  name: ingress-example
  namespace: default
spec:
  servers: 2
  agents: 3
  token: test
  version: v1.26.0-k3s2
  expose:
    ingress:
      enabled: true
      ingressClassName: "nginx"

For Ingress expose k3k needs to support multiple options including:

• ingress class name
• auto configuration for ssl passthrough for multiple ingress controllers