Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you may not be able to execute some actions.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

What is the PF field in k9s?

E
elysha last edited by

In k9s (kubernetes management tool) what is the PF column (for pods)? What does the Ⓕ value mean?
Reply Quote 0
1 Reply Last reply
carriann last edited by

The "PF" field refers to port forwarding.

You may setup port forwarding, ("shift-f" in pod view). This indicator probably means you have setup some port forwarding -- in my case, it prints some weird character.

Although to be honest ... I only figured it out, searching their git repository history .... Introduced here: https://github.com/derailed/k9s/commit/f1111174aa8df815e25b0a029ba1465d3a855b49#diff-5b19eaab395254884c7dff045b0e50a599c29794e80a81fe42c9667450b6e9d4
Reply Quote 0
1 Reply Last reply

kubernetes 663

2
Posts

0
Views

Suggested Topics

K

".format(name, e)) ... google.protobuf.json_format.ParseError: Failed to parse textPayload field: expected string or bytes-like object." GCF logging
Continuous Integration and Delivery (CI, CD) • logging google cloud platform • • Kadyn

2

0
Votes

2
Posts

0
Views

P

Workaround You can cast all of your exceptions (and errors) to string. Example except Exception as e: logger.log_text(str(e)) raise This is still a strange workaround, I would have expected the module to have a better way for this. I tried https://github.com/googleapis/google-cloud-python/issues/6217 and it did not work. Any other ideas welcome.
Z

Is it possible to template JIRA issues with pre-filled field contents?
Continuous Integration and Delivery (CI, CD) • jira templating • • zymir

2

0
Votes

2
Posts

1
Views

B

I don't think you will be able to get far without any plugins. What you can take a look at is the Default Values for 'Create Issue' screen plugin. We were using it in the past, however gave up because defaults could be set only per issue type, and no other conditions. I was in contact with the supplier, though, and they confirmed that defaults per user and other extensions were on their roadmap. Makes sense to check if they are already available.
R

What should I enter in Username & Password fields for recently installed Jenkins setup?
Continuous Integration and Delivery (CI, CD) • jenkins • • Rossere

2

0
Votes

2
Posts

1
Views

T

If you see this Unlock Jenkins To ensure Jenkins is securely set up by the administrator, a password has been written to the log (not sure where to find it?) and this file on the server: /Users/Shared/Jenkins/Home/secrets/initialAdminPassword Please copy the password from either location and paste it below. or something like this, then you need to get the initialAdminPassword and then login and then set a password. Please see the steps here to do so Also, sudo passwd jenkins should prompt you to set a password.
C

Does active choice reactive parameter support hide fields option?
Continuous Integration and Delivery (CI, CD) • jenkins pipeline • • chanisef

2

0
Votes

2
Posts

1
Views

No, this is not possible, because the number and type of parameters for a build are fixed and cannot be modified on-the-fly. The only way to modify which parameters show up in the "build with parameters" UI is to change the job configuration, which alters the parameters permanently. In my opinion, if you need to do several different tasks which require several different input parameters (such as "build", "test", "install", "deploy", etc.), you should have separate jobs in Jenkins for each task. I personally think it is a good ideal in general to avoid complex Jenkins jobs which require a lot of input parameters and try instead to simplify job configuration in order to reduce the likelihood of subtle, difficult-to-debug errors when executing jobs.
N

Auto build and upload to AWS new docker image after commit in repo
Continuous Integration and Delivery (CI, CD) • docker kubernetes automation • • Nykeriab

2

0
Votes

2
Posts

1
Views

A

how can I automate this process? I have an script to push dockerimage to AWS through ecr. You are on the right track. Yes, this should be an automated process from Git push or when someone merge a Pull Request. An important aspect of this is that this "automated process" should be on a dedicated system - such that it is repeatable in a consistent way. Typically this is called a "Continuous Integration Server" or just "Build Server". Some popular choices for this kind of process: Jenkins - old but popular Tekton - Kubernetes native - but still in development GitHub Actions - probably most interesting if your Git repo is on GitHub Bitbucket Pipelines - probably most interesting if your Git repo is Bitbucket AWS CodeBuild - limited but may be interesting if you use AWS GitLab CI - probably most interesting if your Git repo is on GitLab What you need to do is to configure your Git repository system (e.g. GitHub, Bitbucket, Gitlab or AWS CodeCommit) to initiate Pipelines on the Build system (a product of those listed above)
E

how to control pod termination speed in kubernetes
Continuous Integration and Delivery (CI, CD) • kubernetes • • emerson

2

0
Votes

2
Posts

1
Views

E

There is a default grace period for pod termination of 30 seconds. See: https://kubernetes.io/docs/concepts/workloads/pods/pod/#termination-of-pods. You can customize the grace period setting terminationGracePeriodSeconds at the pod spec level.
R

Work item rules in Azure DevOps board: Parent STATUS (custom field) dependent on child STATUS
Continuous Integration and Delivery (CI, CD) • automation azure devops • • rielyn

2

0
Votes

2
Posts

1
Views

E

I think the simplest way to do this would be to utilise a webhook on your Azure DevOps Boards and have it updated via the DevOps API. With a simple serverless instance like Azure Functions you should be able to do this quickly and painlessly.
A

error validating data: ValidationError(Deployment): unknown field "spec" in
Continuous Integration and Delivery (CI, CD) • kubernetes yaml • • Avante

2

0
Votes

2
Posts

1
Views

E

Sure enough, everything and including the last spec: needed to be tabbed to the left once: apiVersion: apps/v1 kind: Deployment metadata: name: client-deployment spec: replicas: 3 selector: matchLabels: component: web template: metadata: labels: component: web spec: containers: - name: client image: ldco2016/multi-client ports: - containerPort: 3000 Unfortunately, you can't tell the difference with how yaml is formatted when pasted here, so it would not have been an easy catch, but if you would be looking at the original file configuration you would have noticed it like I did when I looked a third time.
K

How to properly escape brackets in ArgoCD?
Continuous Integration and Delivery (CI, CD) • kubernetes yaml helm • • kalena

2

0
Votes

2
Posts

0
Views

R

Try this "beauty": {{ "'{{steps.scheduler.outputs.result}} =~ example'" }} {{ "" }} - instructs go template to consider anything within as a literal ' - is a faint attempt to keep it as a string value in YAML; it should be optional
J

One Repository for Kubernetes configuration or one configuration per application repository
Continuous Integration and Delivery (CI, CD) • configuration kubernetes configuration management • • juvenalb

2

0
Votes

2
Posts

1
Views

K

If you're just migrating I'd also recommend using helm. When using helm create the chart definition within the source code repository of the application, https://helm.sh/docs/helm/helm_create/. With an increasing number of services it can become harder and harder to manage so people have started to embrace a "monorepo" that contains a definition of the all the helm charts they currently have deployed and their respective versions. This way you can easily track when a version of service A was bumped and when a version of service B was bumped. https://www.infracloud.io/blogs/monorepo-ci-cd-helm-kubernetes/
T

How can I get everything to use the same load balancer on DigitalOcean?
Continuous Integration and Delivery (CI, CD) • kubernetes load balance • • Trenton

2

0
Votes

2
Posts

0
Views

K

A service is a way to route traffic to an internal IP. By internal I mean inside Kubernetes. I mean you don't really point it to an IP, you point it to a deployment or w/e and Kubernetes takes care of the IP and routing traffic for you to the pods that make up that deployment. Now not all services work the same. ClusterIP will create an internal hostname and then route traffic to the Pods's IP. This make the service only reachable from other pods inside the cluster. Then you have NodePort, which opens a port on all worker nodes and routes the traffic to the deployment/pods or w/e. This exposes the service externally. So now it's reachable by a worker nodes IP and whatever port was selected by the service. You can also hard code a port but I wouldn't recommend it. But who wants to deal with IP's and port numbers? Thats lame. We want hostnames. you know like myapp.dev.coolcompany.com or w/e. That is where a Loadbalancer comes in. If you have a cluster running on a cloud provider then your cluster is likely already setup to use a LoadBalancer service. This service does two things. First it creates a nodePort service and then it configured a load balancer on your cloud provider to point traffic to all worker nodes and the NodePort for your service. When your LoadBalncer is created it likely came with a public DNS name to reach it by. Now you can just create a DNS record to point from myapp.dev.coolcompany.com -> my.lb.dns.cloudprovider.com. Now your app is reachable externally and without knowing about IP's and ports. Everything I just explained is explained even better and more accurately by the Kubernetes https://kubernetes.io/docs/concepts/services-networking/service/ . You should probably give it a read. So what's an Ingress? Well an Ingress is like creating a "LoadBalancer" but inside the cluster. We call this the Ingress Controler and there are a ton of options like Nginx, Apache and Traeffik to name a few. This likely does not come included by default on your cluster. You will need to create and configure an ingress controller before you can use the "ingress" API object. An ingress controller works like any other deployment running on your cluster. You will need to expose this application externally. Most often using a "LoadBalancer" Service. Confused yet? It will look like this: ExternalLB --> IngressLBService(NodePort) --> IngressController Once your Ingress Controller is configured you can then expose your deployments externally without using a "LoadBalancer" service. You can instead use a "ClusterIP" service + an "ingresss" object configured to point at the service. It will look like this: ExternalLB --> IngressLBService(NodePort) --> IngressController --> DeploymentService(ClusterIP) --> DeploymentPods As you can see the "LoadBalancer" service and IngressController work very similarly. So why do you need an IngressController? Well if your application stack is simple then you probably don't. Some of the cloud providers "LoadBalancers" are pretty feature rich. Like on AWS. But some of these Ingress Controllers offer some pretty nice features. Like path bases routing, integrating with Authentication providers, Automatic TLS certificate provisioning and tracing+montioring etc. Basically, if you need these features and your cloud provider's Loadbalancer doesn't have these things then an Ingress Controller is the best way to get them. Another tiny advantage is that an Ingress can help abstract away the cloud provider. Meaning less vendor lockin. If I have an application that is exposed externally via an Ingress controller then I can re-deploy that application on any cluster on any cloud provider as long as that cluster has an ingress controller. If I'm depending on a "LoadBalancer" service then its likely that service is configured with a bunch of Annotations and that is often not compatible with other clouds. Meaning I cant just redeploy that application to another cloud provider. This use case isn't very important to many people and it wouldn't be a big deal to fix a service to use a different cloud LB but it is something to consider. You can find a lot more in the Kubernetes https://kubernetes.io/docs/concepts/services-networking/ingress/ .
N

Replications in kubernetes between nodes
Software Programming • asp.net c languageore azure kubernetes • • nishika

2

0
Votes

2
Posts

0
Views

you have to add antiaffinity between your pod's example : affinity: podAntiAffinity: requiredDuringSchedulingIgnoredDuringExecution: - labelSelector: matchExpressions: - key: app operator: In values: - apixxx topologyKey: kubernetes.io/hostname
How much memory/cpu to allocate per pod?
Continuous Integration and Delivery (CI, CD) • kubernetes • • Laycee

2

0
Votes

2
Posts

1
Views

G

It's a severe problem to solve if you don't know the performance characteristics of the process you are containerising. There are a couple of approaches you could take that will get you an answer, although you will need to monitor it carefully in production and an adjust the resource limits as required. Approach #1: Educated Guess - take a look around at what other people have done to host a specific process, GitHub is an excellent resource for finding Dockerfiles and their associated Helm Charts. Equally, if someone has done some tests for Virtual Machine sizing, you may be able to derive an answer that is acceptable in the short term. Approach #2: Testing - my personal preference is to test the component in question: The Apache Bench is excellent for quick performance tests against HTTP(S) endpoints Tools such as the MySQL Benchmark tool allow you to test MySQL, many applications have dedicated benchmarking tools. If the software is more complicated you can use tools such as Artillery or Gattling to create a performance test suite that you can use to slam the container and find out how it performs. Whichever approach you take, you will need to make sure that you have a proper monitoring and dashboarding solution working so that you can actually analyse the behaviour of the containers under load and adjust accordingly.
N

Names field in docker ps -a command
Continuous Integration and Delivery (CI, CD) • docker • • nishika

2

0
Votes

2
Posts

0
Views

K

If you don't name a container when you run it Docker will make up a random name for you. This is handy for differentiating different invocations of a container without resorting to hex values. You can see by https://github.com/moby/moby/blob/master/pkg/namesgenerator/names-generator.go all of the possible names that could be generated.
J

which path has to be specified in httpGet handler in kubernetes?
Continuous Integration and Delivery (CI, CD) • kubernetes • • juvenalb

2

0
Votes

2
Posts

0
Views

P

path is used to declare the service's routing address / interface address / API When using livenessProbe.httpGet as a health checker, a health query is required, i.e. it calls a uri to confirm the service health based on the returned status code The composition of this uri: scheme://podIp:port/path == http://10.244.171.183:8080/index.html

What is the PF field in k9s?

Suggested Topics

".format(name, e)) ... google.protobuf.json_format.ParseError: Failed to parse textPayload field: expected string or bytes-like object." GCF logging Continuous Integration and Delivery (CI, CD) • logging google cloud platform • • Kadyn

Is it possible to template JIRA issues with pre-filled field contents? Continuous Integration and Delivery (CI, CD) • jira templating • • zymir

What should I enter in Username & Password fields for recently installed Jenkins setup? Continuous Integration and Delivery (CI, CD) • jenkins • • Rossere

Does active choice reactive parameter support hide fields option? Continuous Integration and Delivery (CI, CD) • jenkins pipeline • • chanisef

Auto build and upload to AWS new docker image after commit in repo Continuous Integration and Delivery (CI, CD) • docker kubernetes automation • • Nykeriab

how to control pod termination speed in kubernetes Continuous Integration and Delivery (CI, CD) • kubernetes • • emerson

Work item rules in Azure DevOps board: Parent STATUS (custom field) dependent on child STATUS Continuous Integration and Delivery (CI, CD) • automation azure devops • • rielyn

error validating data: ValidationError(Deployment): unknown field "spec" in Continuous Integration and Delivery (CI, CD) • kubernetes yaml • • Avante

How to properly escape brackets in ArgoCD? Continuous Integration and Delivery (CI, CD) • kubernetes yaml helm • • kalena

One Repository for Kubernetes configuration or one configuration per application repository Continuous Integration and Delivery (CI, CD) • configuration kubernetes configuration management • • juvenalb

How can I get everything to use the same load balancer on DigitalOcean? Continuous Integration and Delivery (CI, CD) • kubernetes load balance • • Trenton

Replications in kubernetes between nodes Software Programming • asp.net c languageore azure kubernetes • • nishika

How much memory/cpu to allocate per pod? Continuous Integration and Delivery (CI, CD) • kubernetes • • Laycee

Names field in docker ps -a command Continuous Integration and Delivery (CI, CD) • docker • • nishika

which path has to be specified in httpGet handler in kubernetes? Continuous Integration and Delivery (CI, CD) • kubernetes • • juvenalb

".format(name, e)) ... google.protobuf.json_format.ParseError: Failed to parse textPayload field: expected string or bytes-like object." GCF logging
Continuous Integration and Delivery (CI, CD) • logging google cloud platform • • Kadyn

Is it possible to template JIRA issues with pre-filled field contents?
Continuous Integration and Delivery (CI, CD) • jira templating • • zymir

What should I enter in Username & Password fields for recently installed Jenkins setup?
Continuous Integration and Delivery (CI, CD) • jenkins • • Rossere

Does active choice reactive parameter support hide fields option?
Continuous Integration and Delivery (CI, CD) • jenkins pipeline • • chanisef

Auto build and upload to AWS new docker image after commit in repo
Continuous Integration and Delivery (CI, CD) • docker kubernetes automation • • Nykeriab

how to control pod termination speed in kubernetes
Continuous Integration and Delivery (CI, CD) • kubernetes • • emerson

Work item rules in Azure DevOps board: Parent STATUS (custom field) dependent on child STATUS
Continuous Integration and Delivery (CI, CD) • automation azure devops • • rielyn

error validating data: ValidationError(Deployment): unknown field "spec" in
Continuous Integration and Delivery (CI, CD) • kubernetes yaml • • Avante

How to properly escape brackets in ArgoCD?
Continuous Integration and Delivery (CI, CD) • kubernetes yaml helm • • kalena

One Repository for Kubernetes configuration or one configuration per application repository
Continuous Integration and Delivery (CI, CD) • configuration kubernetes configuration management • • juvenalb

How can I get everything to use the same load balancer on DigitalOcean?
Continuous Integration and Delivery (CI, CD) • kubernetes load balance • • Trenton

Replications in kubernetes between nodes
Software Programming • asp.net c languageore azure kubernetes • • nishika

How much memory/cpu to allocate per pod?
Continuous Integration and Delivery (CI, CD) • kubernetes • • Laycee

Names field in docker ps -a command
Continuous Integration and Delivery (CI, CD) • docker • • nishika

which path has to be specified in httpGet handler in kubernetes?
Continuous Integration and Delivery (CI, CD) • kubernetes • • juvenalb