Ref: https://github.com/harvester/harvester/issues/761
Verify Items
- generated kubeconfig is able to access kubenetes API
- new node able to join the cluster using the configured Domain Name
- create node with ssl-certificates settings is working as expected.
Case: Kubeconfig
- Install Harvester with at least 2 nodes
- Generate self-signed TLS certificates from https://www.selfsignedcertificate.com/ with specific name
- Navigate to advanced settings, edit
ssl-certificates
settings - Update generated
.cert
file to CA and Public Certificate,.key
file to Private Key - Relogin with domain name
- Navigate to Support page, then Click Download KubeConfig, file should named
local.yaml
- Kubernetes API should able to be accessed with config
local.yaml
(follow one of the instruction for testing)
Case: Host joining with https and Domain Name
- Install Harvester with single node
- Generate self-signed TLS certificates from https://www.selfsignedcertificate.com/ with specific name
- Navigate to advanced settings, edit
ssl-certificates
settings - Update generated
.cert
file to CA and Public Certificate,.key
file to Private Key - Install another Harvester Host as a joining node via PXE installation
- the
server_url
MUST be configured as the specific domain name - Be aware set
os.dns_nameservers
to make sure the domain name is reachable.
- the
- The joining node should joined to the cluster successfully.
Case: Host creating with SSL certificates
- Install Harvester with single node via PXE installation
- fill in
system_settings.ssl-certificates
as the format in https://github.com/harvester/harvester/issues/761#issuecomment-993060101
- fill in
- Dashboard should able to be accessed via VIP and domain name