Skip to main content
Version: 5.0.0

Building a Complete Application Service Using a Private Image

Building Service Image​

helm Installation​

https://github.com/helm/helm/releases

Install helm v3.9 (proxy required).

Log in to the Image Repository​

This step is to pull the image during packaging:

sealos login registry.cn-hangzhou.aliyuncs.com -u username -p password

Modify helm chart​

Download helm chart template:

git clone https://github.com/luanshaotong/scienson_osm.git
templates/deploy.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  labels:
    run: avatarsolver-osm
  name: avatarsolver-osm
spec:
  replicas: { { .Values.osm.replicas } }
  selector:
    matchLabels:
      run: avatarsolver-osm
  template:
    metadata:
      labels:
        run: avatarsolver-osm
    spec:
      containers:
        - image: registry.cn-hangzhou.aliyuncs.com/scienson/avatarsplver-osm:2022-07-11-21-05
          name: app
          ports:
            - containerPort: 7001
              protocol: TCP
            - containerPort: 8080
              protocol: TCP
          resources:
            limits:
              cpu: 2
              memory: 6144Mi
            requests:
              cpu: 1
              memory: 4096Mi

Resolve service via domain name:

templates/service.yaml
apiVersion: v1
kind: Service
metadata:
  name: osm-service
spec:
  type: ClusterIP
  selector:
    run: avatarsolver-osm
  ports:
    - name: osm
      port: 7001
      targetPort: 7001

Expose service to the public network:

templates/ingress.yaml
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: osm-ingress
spec:
  ingressClassName: nginx
  rules:
    - host: www.abc.com
      http:
        paths:
          - pathType: Prefix
            path: /
            backend:
              service:
                name: osm-service
                port:
                  number: 80

Mainly used to render the number of replicas:

values.yaml
osm:
  replicaCount: 1

Package helm chart​

helm package .

Modify image list​

cat images/shim/osm
registry.cn-hangzhou.aliyuncs.com/scienson/avatarsplver-osm:2022-07-11-21-05

Modify Dockerfile​

FROM scratch
COPY . .
CMD ["helm install osm scienson-osm-0.1.1.tgz --namespace osm --create-namespace"]

Build Image​

sealos build -f Dockerfile -t docker.io/luanshaotong/osm:v0.1.1 .

Test Deployment​

sealos run labring/kubernetes:v1.25.0 labring/helm:v3.8.2 labring/calico:v3.24.1  --masters 

172.31.37.111
kubectl taint no node-role.kubernetes.io/master:NoSchedule-
kubectl taint no node-role.kubernetes.io/control-plane:NoSchedule-
sealos run labring/ingress-nginx:4.1.0
sealos run docker.io/luanshaotong/osm:v0.1.1

Notice: labring/helm should be set before labring/calico. If every step of the application installation goes smoothly, that's it. Otherwise, you may need to debug and clean up the cluster for reinstallation.

Other Issues​

Cleaning Up the Cluster​

If there are problems and you need to clean up the cluster:

sealos reset
rm /root/.sealos -rf

You can then reinstall.