aws-eks

问题 I have a cluster with 2 node groups: real time and general . I would like only pods which tolerate affinity real time to be able to run on nodes from the real time cluster. My approach was to taint the relevant nodes and add toleration to the pod that I want to register to that node. I came into a dead-end when I was trying to taint a node-group. In my case I have an EKS node group that is elastic, i.e. nodes are increasing and decreasing in numbers constantly. How can I configure the group

问题 I am trying to run a pod on fargate from EKS that needs to access s3 via boto3 python client and I cant figure out why this is happening. It works just fine when scheduled on a eks ec2 node. botocore.exceptions.NoCredentialsError: Unable to locate credentials I have a properly setup fargate profile and followed this guide. Does anyone know why aws credentials are not within the context of this pod? Does this have anything to do with the pod execution role? 回答1: I have a properly setup fargate

问题 I am trying to run a pod on fargate from EKS that needs to access s3 via boto3 python client and I cant figure out why this is happening. It works just fine when scheduled on a eks ec2 node. botocore.exceptions.NoCredentialsError: Unable to locate credentials I have a properly setup fargate profile and followed this guide. Does anyone know why aws credentials are not within the context of this pod? Does this have anything to do with the pod execution role? 回答1: I have a properly setup fargate

问题 I have an EKS cluster to which I've added support to work in hybrid mode (in other words, I've added Fargate profile to it). My intention is to run only specific workload on the AWS Fargate while keeping the EKS worker nodes for other kind of workload. To test this out, my Fargate profile is defined to be: Restricted to specific namespace (Let's say: mynamespace ) Has specific label so that pods need to match it in order to be scheduled on Fargate (Label is: fargate: myvalue ) For testing k8s

问题 I have deployed istio in my eks cluster with demo profile. demo has kiali deployment with it. The access secret for kiali dashboard is ( username:admin , password:admin ).I was able to access my dashboard with this credentials. Then I created my own secrets. $ echo shajaltest | base64 $ c2hhamFsdGVzdAo= Deleted the secrets for kiali. $ kubectl delete secrets kiali -n istio-system Deployed the secrets again with this yaml apiVersion: v1 kind: Secret metadata: name: kiali namespace: istio

问题 I'm currently using Kubernetes Client Plugin in Jenkins but still it's confusing to configure, because it looks for Kubernetes config, and those credetials are not available even I configured them in the credentials section. Please see the screenshot below for my credentials which are configure in my Jenkins. When I do try to add those credentials from Jenkins side, which is not listed under the Kubernetes credentials. The red colored are has no kist of my credentials. How can I configure

问题 I'm currently using Kubernetes Client Plugin in Jenkins but still it's confusing to configure, because it looks for Kubernetes config, and those credetials are not available even I configured them in the credentials section. Please see the screenshot below for my credentials which are configure in my Jenkins. When I do try to add those credentials from Jenkins side, which is not listed under the Kubernetes credentials. The red colored are has no kist of my credentials. How can I configure

问题 I'm currently using Kubernetes Client Plugin in Jenkins but still it's confusing to configure, because it looks for Kubernetes config, and those credetials are not available even I configured them in the credentials section. Please see the screenshot below for my credentials which are configure in my Jenkins. When I do try to add those credentials from Jenkins side, which is not listed under the Kubernetes credentials. The red colored are has no kist of my credentials. How can I configure

问题 I'm currently using Kubernetes Client Plugin in Jenkins but still it's confusing to configure, because it looks for Kubernetes config, and those credetials are not available even I configured them in the credentials section. Please see the screenshot below for my credentials which are configure in my Jenkins. When I do try to add those credentials from Jenkins side, which is not listed under the Kubernetes credentials. The red colored are has no kist of my credentials. How can I configure

问题 I'm currently using Kubernetes Client Plugin in Jenkins but still it's confusing to configure, because it looks for Kubernetes config, and those credetials are not available even I configured them in the credentials section. Please see the screenshot below for my credentials which are configure in my Jenkins. When I do try to add those credentials from Jenkins side, which is not listed under the Kubernetes credentials. The red colored are has no kist of my credentials. How can I configure