-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathconfig
45 lines (42 loc) · 2.89 KB
/
config
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
apiVersion: v1
kind: Config
preferences: {}
#
# Add any number of kubernetes clusters here
# - Extract your Certificate Authority Data from the relevant cluster
# on a kubeadm created cluster you could find it in /etc/kubernetes/admin.conf
# on the first control-plane node
# - Expose your API so that your users can access it via a jumphost, VPN or other aproperiate mechanism - update the server URL accordingly
#
clusters:
- cluster:
certificate-authority-data: LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSURCVENDQWUyZ0F3SUJBZ0lJWlpKTFE0UFBBbVl3RFFZSktvWklodmNOQVFFTEJRQXdGVEVUTUJFR0ExVUUKQXhNS2EzVmlaWEp1WlhSbGN6QWVGdzB5TlRBeE1Ea3hNekF5TkRKYUZ3MHpOVEF4TURjeE16QTNOREphTUJVeApFekFSQmdOVkJBTVRDbXQxWW1WeWJtVjBaWE13Z2dFaU1BMEdDU3FHU0liM0RRRUJBUVVBQTRJQkR3QXdnZ0VLCkFvSUJBUURDSlZYUXpaVmJFWS90Yk10WGU1Qis4S2JTM1d2TjdLbmU2Y0lkMDBHcG1zcTE4dVRUQnJnRDBPam8Kb3JvUXk5NFNuSjAwamFqUzdDaElsaUR1bHREd2pjU1FkZFUrWlR0dCt6eDlvV24zTlVFc1lrSUR4a3VsREx6QgpxNVc2YnpWY1lHU2JmejRCQkFJbmxlcmJkb2hRdVozYno1SXJHOXUxZkFlMjNZQ2NsZnFvbU40c0V2Yi9aL1JMClY3Tm5oSzdIak1wU0drZzcvRk1Gd0VOSFZJK2N4djZlWnUrdDVnV1Bkc3ZtVjAzNXJIR2xoVHFydXVGaHFaR2EKd3J1N1hhb2JtVHdMRlVpQ3FPK0pOZ25JTElNdXc5MU1PZDlnNXNVS3pPdTlkdlo0RGd2emtCbWFpRXFEUFljRAp5eGNvN0ZpRkQ1UjZDM3ZvYm9mbXByK3lDZjd4QWdNQkFBR2pXVEJYTUE0R0ExVWREd0VCL3dRRUF3SUNwREFQCkJnTlZIUk1CQWY4RUJUQURBUUgvTUIwR0ExVWREZ1FXQkJSdlVzM0JGVEJvM1UvUGQrWm8rZmdrbjQ5US9qQVYKQmdOVkhSRUVEakFNZ2dwcmRXSmxjbTVsZEdWek1BMEdDU3FHU0liM0RRRUJDd1VBQTRJQkFRQVRJbExXUTVyMAozYkhVS1NaOURoRmJFMTRNSFFGbTVZRlZsTGNoUFVkMlJhQ1ZnWVVuc0VFaW53TUdMSnpJck5jL3ppbkU4QllwCms2cGlIckticjU0dnU0LzhYL1hjM09CaGs3eWFjSDlaaUZYU0ZMa2lEN2k5dnZLNXI5QU9sRWVYY3ppNUZYZWYKa2VRQTZUSmxKZFpoL0NIdXJyeTUvTk1wa3E4blN4Z0p5cTg4T2tCd3pQSTNKU0gwcy9CZW1jeTNNV1A0dEREOApIaFc4TkRubUREcTVRSHExYytSUHY2eTgxTzR5T3NNYm9HUmpUQnVMYWgzdkxzRjQveWx0cm5FY0RMV3JTUDlMClE3VVRPYnVrNy94YXdGejQvVTBuTlVjS08zQ0JDQldtNWx4ZDZvZHVwVmJEVFA0NHlNT2t1ZU5HTDB5TXRpakQKRzl6Vm4rNDhaQndnCi0tLS0tRU5EIENFUlRJRklDQVRFLS0tLS0K
server: https://cluster.example.com:6443
name: k8s.met.no
#
# Any OpenIDConnect provider should do - here is an example using google login
# Update CLIENT_ID and CLIENT_SECRET for use with google (and also IDP_ISSUER_URL if you are using another provider)
#
users:
- name: google-login
user:
exec:
apiVersion: "client.authentication.k8s.io/v1beta1"
command: /usr/local/bin/kubekey
env:
- name: CLIENT_ID
value: 605222161680-h15ydfp5zhxp1cjzlzazphq1kptyejam.apps.googleusercontent.com
- name: CLIENT_SECRET
value: SVLHacFXLeuJxlIPNciOeFzl
- name: IDP_ISSUER_URL
value: https://accounts.google.com
#
# Contexts just refences other sections in this configuration file, update names to match
# what you have used above. Notice that you could also set a current-context by name
#
contexts:
- context:
cluster: cluster.example.com
user: google-login
name: cluster.example.com
current-context: cluster.example.com