Skip to content
This repository has been archived by the owner on Apr 25, 2023. It is now read-only.

Commit

Permalink
Merge pull request #1072 from yamt/k3s-v0.7.0
Browse files Browse the repository at this point in the history
fix-ca-for-k3s.sh: document that k3s v0.7.0 no longer needs this
  • Loading branch information
k8s-ci-robot authored Aug 1, 2019
2 parents cf27d73 + fbde7c0 commit 99be021
Showing 1 changed file with 7 additions and 2 deletions.
9 changes: 7 additions & 2 deletions scripts/fix-ca-for-k3s.sh
Original file line number Diff line number Diff line change
Expand Up @@ -19,20 +19,25 @@
#
# Description:
# This script fixes up the configuration for member clusters
# running k3s. (https://k3s.io/)
# running older versions of k3s (< v0.7.0). (https://k3s.io/)
# Namely it updates caBundle for the member clusters to match with
# the ones in KUBECONFIG. It's intended to be run after joining
# member clusters successfully.
# Note that this is not necessary for k3s v0.7.0.
#
# Background:
# In k3s, different endpoints and certificates are configured for
# In k3s < v0.7.0, different endpoints and certificates are configured for
# users (KUBECONFIG) and pods (service accounts).
# Because "kubefedctl join" uses the endpoint from KUBECONFIG and
# the certificate from a service account in the member cluster,
# the kubefed controller manager fails to communicate with the
# member clusters, producing the messages like the following.
#
# x509: certificate signed by unknown authority
#
# k3s v0.7.0 has been changed to use the same CA cert to sign them. [1]
# Thus this workaround is no longer necessary.
# [1] https://github.com/rancher/k3s/commit/2c9444399b427ffb706818f5bf3892a8880673bf

set -o errexit
set -o nounset
Expand Down

0 comments on commit 99be021

Please sign in to comment.