Tag: #yaml

Open the door for root users in Red Hat OpenShift (example StatefulSet)¶

Leave a comment

This “blog post"/"cheat sheet” is about “Open the door for root users in OpenShift (example StatefulSet)”. The topic is in context of two blog posts I wrote called Run a PostgreSQL container as a non-root user in OpenShift and Open the door for root users in Red Hat OpenShift¶.

If you want to get an overview of the existing Default OpenShift security context constraints visit the IBM Cloud documentation.

Continue reading →

Open the door for root users in Red Hat OpenShift (example Deployment)¶

1 Comment

This “blog post"/"cheat sheet” is about “Open the door for root users in OpenShift“. The topic is in context of an older blog post I wrote called Run a PostgreSQL container as a non-root user in OpenShift. Let’s look for the opposite perspective in this blog post.

If you want to get an overview of the existing Default OpenShift security context constraints visit the IBM Cloud documentation.

Continue reading →

error: no matches forkind “Deployment”in version “apps/v1beta1”

3 Comments
This is a short blog post about changes in the new Kubernetes deployment definition.
In my older blog posts related to Kubernetes you will find older deployment definitions, these definitions will cause errors during the Kubernetes deployment. Here are the two major problems you maybe will notice:

1. If you get the following error

error: unable to recognize "deployment.yaml": 
no matches forkind "Deployment"in version "apps/v1beta1"
Please change the entry apps/v1beta1 to apps/v1 in the deployment.yaml file, the newer `deployment definition` for Kubernetes v1.16.8 (v1.18).

Note: Additional useful blog post here.

2. If you get this error

error: error validating "deployment.yaml": 
error validating data: ValidationError(Deployment.spec): 
missing required field "selector"in io.k8s.api.apps.v1.DeploymentSpec; 
#if you choose to ignore these errors, 
turn validation off with --validate=false
You need to insert in the deployment specification the statement selector:matchLabels:name:authors, as you see in the table below.
The table contains an example of the major changes in the deployment specification, the left hand side contains the new Kubernetes deployment definition and right hand side includes the older definition. The `selector` is now required.
kind: Deployment
apiVersion: apps/v1
metadata:
   name: authors
   labels:
     app: authors
spec:
   selector:
     matchLabels:
       app: authors
       version: v1
  replicas: 1
  template:
    metadata:
     labels:
        app: authors
        version: v1
     spec:
       containers:
       - name: authors
         image: authors:1
         ports:
          - containerPort: 3000
 ...
 
kind: Deployment
apiVersion: apps/v1beta1
metadata:
  name: authors
  labels:
    app: authors
spec: 
  ...
  ...
  ...
  ...
  replicas: 1
  template:
  metadata:
    labels:
      app: authors
        version: v1
    spec:
      containers:
      - name: authors
        image: authors:1
        ports:
        - containerPort: 3000
...

I hope this was useful for you and let’s see what’s next?

Greetings,

Thomas

PS:  You can try out Cloud Foundry Apps or Kubernetes on IBM Cloud. By the way, you can use the IBM Cloud for free, if you simply create an IBM Lite account. Here you only need an e-mail address.

#Kubernetes, #Deployment, #yaml

 

Deploy a container image to Kubernetes – a short teaser video

Leave a comment

Today I recorded part 3 of my   “Let’s get started with cloud native Java applications on Kubernetes hands-on workshop”  3-minutes teaser videos series on youtube.

This short 3-minute teaser video is about: deploy a container image to Kubernetes in context of the cloud native starter project and workshop on GitHub project.

Check it out:

You can get more detailed information about the topic: deploy a container image to Kubernetes in one of my blog posts.

Continue reading →