cluster-api | Home for Cluster API , a subproject of sig-cluster-lifecycle | Continuous Deployment library
kandi X-RAY | cluster-api Summary
kandi X-RAY | cluster-api Summary
Cluster API is a Kubernetes sub-project focused on providing declarative APIs and tooling to simplify provisioning, upgrading, and operating multiple Kubernetes clusters. Started by the Kubernetes Special Interest Group (SIG) Cluster Lifecycle, the Cluster API project uses Kubernetes-style APIs and patterns to automate cluster lifecycle management for platform operators. The supporting infrastructure, like virtual machines, networks, load balancers, and VPCs, as well as the Kubernetes cluster configuration are all defined in the same way that application developers operate deploying and managing their workloads. This enables consistent and repeatable cluster deployments across a wide variety of infrastructure environments.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of cluster-api
cluster-api Key Features
cluster-api Examples and Code Snippets
Community Discussions
Trending Discussions on cluster-api
QUESTION
I am trying to access the metrics server for a k8s cluster without the use of kubectl proxy
. After finding the tutorial at https://kubernetes.io/docs/tasks/administer-cluster/access-cluster-api/#without-kubectl-proxy, I've run into an issue.
When making the request curl -X GET $APISERVER/apis/metrics.k8s.io/v1beta1/nodes --header "Authorization: Bearer $TOKEN" --insecure | jq
I get the following permissions error:
ANSWER
Answered 2021-Feb-15 at 17:30I figured out it was the apiGroups
that needed to be modified. The following ClusterRole and ClusterRoleBinding worked:
QUESTION
With the kubectl
command line, I can run commands in a given context using the --context
flag, such as:
ANSWER
Answered 2020-Dec-19 at 03:44you can read the contexts from the file and pass it to the CoreV1Api
function like below
QUESTION
I've an issue while using SWITCH on a Jenkinsfile. When the PR is done the pipeline is started using println I see the CHANGE_TARGET is correct to match the CASE condition, however it apply master and all variables are set using the MASTER case values.
the first println return:
The build ENV is test | PR Title: XXX
code example:
...ANSWER
Answered 2020-Aug-13 at 14:43You are missing break
at the end of every case. When there is no break
, Groovy continues and runs the code from the remaining cases.
QUESTION
I am implementing a cluster-api controller using Kubernetes as the infrastructure provider - that is, I am trying to run Kubernetes Nodes as Kubernetes Pods and form a cluster within a cluster.
I have this working apart from network connectivity between Pods of the inner cluster (running on Pods of the infrastructure cluster), but I am stuck as to what the issue is.
I am running on GKE, using their default CNI implementation. I am then attempting to use Calico for an overlay implementation of the inner cluster, using IP-in-IP encapsulation so the Nodes of the infrastructure cluster do not need to know how to route inner cluster Pod IPs.
I am creating the infrastructure cluster as follows (the UBUNTU image is needed for the ipip
kernel module required by Calico's IP-in-IP encapsulation.
ANSWER
Answered 2020-Jan-06 at 16:31It was necessary to allow ipencap
protocol on the GKE nodes:
QUESTION
I'm trying to use Kubernetes Go-Client in my program (which will run outside my Kubernetes cluster) which requires access to config file. The config file requires some token, service account details etc so that the program can access the Kubernetes cluster.
The config file is of the form below:
...ANSWER
Answered 2019-Dec-16 at 14:18Thanks Markus for the hint link.
I am writing the answer in Go as the original link showed how to do it from command line. The steps are as follows:
- Replace the fields to be modified in the file with something of the form
${X}
. In my case e.g. I replacedmy-token
with${my-token}
and so on. - Here you can set
X
as an environment variable so that your code can access it during runtime. e.g. by doingexport X="abcd"
in command line. - Say the file name is
config
. - Execute the following code:
QUESTION
I have setup a kubernetes
cluster from scratch. This just means I did not use services provided by others, but used the k8s installer it self. Before we used to have other clusters, but with providers and they give you tls cert and key
for auth, etc. Now this cluster was setup by myself, I have access via kubectl
:
ANSWER
Answered 2019-Oct-23 at 06:59You need to setup RBAC for the user. define roles and rolebinding. follow the link for reference -> https://docs.bitnami.com/kubernetes/how-to/configure-rbac-in-your-kubernetes-cluster/
QUESTION
Please refer to the above image, I am trying to access Kubernetes Clusters Using the Kubernetes API and for that purpose as mentioned in documents I am using Python Kuberentes Client, that needs a token to communicate with Kube API
.
When I am trying to authenticate the user with the token added in Kube-config
file by Kube login everything works fine, where token provided by Keycloak
REST API results in an un-authorization error.
I would be glad if anyone could provide any insight on this issue.
...ANSWER
Answered 2019-May-08 at 15:16We have resolved the issue, below are our findings and their resolution:
- There was a discrepancy in the token generated with KubeLogin client and Keycloak Rest API, issuer URL is hostname in the token generated with KubeLogin whereas in the token generated with Keycloak Rest API issuer URL is IP Address.
- Also, In our(Keycloak instance) generated certificate, we have hostname as issuer name which might be the reason for getting un-authorization errors. We reconfigured the Keycloak with new certificates which have DNS name.
- We had to create RBAC with cluster scope.
QUESTION
From the Kubernetes docs (Accessing the API from a Pod):
The recommended way to locate the apiserver within the pod is with the kubernetes DNS name, which resolves to a Service IP which in turn will be routed to an apiserver.
However, this 'kubernetes' dns name does not appear to exist when I was in the shell of an OpenShift pod. I expected it to exist by default due the Kubernetes running underneath, but am I mistaken? This was using OpenShift Container Platform version 3.7.
Is there a standard way to access the apiserver short of passing it in as an environment variable or something?
...ANSWER
Answered 2018-Apr-17 at 03:45In OpenShift, you can use:
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install cluster-api
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page