One of the great advantages of SAP Kyma is the fact that as long as your planned work load is on top of the internet protocol there are virtually no limits on what you deploy.
Dockerfile
in that folder and open it in the editor. I suggest to build it upon a Java 11 image which is still very lean.#Build SAP Cloud Connector image
FROM bitnami/java:11-debian-10
WORKDIR /usr/sapcc
COPY . /home
RUN apt update && \
apt install lsof && \
apt install nano
EXPOSE 8443/tcp
$ docker build -t <your-registry-and-username>/java11-sapcc:1.0 .
$ docker push <your-registry-and-username>/java11-sapcc:1.0
sap-cc-deployment.yaml
. Looking at how to build the deployment we go step by step.apiVersion: v1
kind: Namespace
metadata:
name: dl-sapcc
labels:
istio-injection: disabled
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: sapcc-pvc
namespace: dl-sapcc
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 1Gi
---
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: sap-cloud-connector
namespace: dl-sapcc
spec:
replicas: 1
selector:
matchLabels:
app: sapcc-app
template:
metadata:
labels:
app: sapcc-app
spec:
containers:
- name: sap-cc-image
image: <your-registry-and-username>/java11-sapcc:1.0
imagePullPolicy: Always
ports:
- containerPort: 8443
resources:
requests:
memory: "512Mi"
cpu: "250m"
limits:
memory: "1Gi"
cpu: "500m"
volumeMounts:
- mountPath: /usr/sapcc
name: sapcc-volume
command: ["/bin/sh"]
args: ["-c", "if [ ! -f /usr/sapcc/go.sh ]; then tar -xzof /home/sapcc*.tar.gz && rm /home/*.tar.gz; else echo Already installed, starting; fi; ./go.sh"]
volumes:
- name: sapcc-volume
persistentVolumeClaim:
claimName: sapcc-pvc
---
apiVersion: v1
kind: Service
metadata:
labels:
app: sapcc-app
name: sappcc-service
namespace: dl-sapcc
spec:
ports:
- name: "adminport"
port: 8443
targetPort: 8443
type: LoadBalancer
selector:
app: sapcc-app
apiVersion: v1
kind: Service
metadata:
annotations:
dns.gardener.cloud/dnsnames: dlcc.<your-kyma-cluster-name>.k8s-hana.ondemand.com
dns.gardener.cloud/ttl: "600"
dns.gardener.cloud/class: garden
labels:
app: sapcc-app
name: sappcc-service
namespace: dl-sapcc
spec:
ports:
- name: "adminport"
port: 8443
targetPort: 8443
type: LoadBalancer
selector:
app: sapcc-app
$ kubectl apply -f sapcc-deployment.yaml
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Subject | Kudos |
---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
User | Count |
---|---|
40 | |
25 | |
17 | |
13 | |
8 | |
7 | |
7 | |
7 | |
6 | |
6 |