Skip to main content

Nexus installation on EKS

  • Create nexus namespace
    •                         
apiVersion: v1
kind: Namespace
metadata:
  name: nexus
  • Create storage class for nexus to store data on AWS EBS
    •                         
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: nexus
provisioner: kubernetes.io/aws-ebs
parameters:
  type: gp2
  fsType: ext4
allowVolumeExpansion: true
  • Create persistent volume claim
    •                         
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: nexus
  namespace: nexus
  labels:
    app: nexus
spec:
  storageClassName: nexus
  resources:
    requests:
      storage: 50Gi
  accessModes:
    - ReadWriteOnce
  • Create deployment for pod, replicaset and deployment itself.
    Since, nexus's docker registry accessible on separate ports, hence as per requirement add number of ports for docker registry.
    •                     
apiVersion: apps/v1beta1
kind: Deployment
metadata:
  name: nexus
  namespace: nexus
spec:
  replicas: 1
  template:
    metadata:
      name: nexus
      labels:
        app: nexus
    spec:
      securityContext:
        fsGroup: 2000
      containers:
      - image: sonatype/nexus3:latest
        name: nexus
        imagePullPolicy: IfNotPresent
        resources:
          requests:
            memory: 1Gi
            cpu: 500m
          limits:
              memory: 1Gi
              cpu: 500m
        ports:
          - containerPort: 8081
            protocol: TCP
            name: nexus-ui
          - containerPort: 8082
            protocol: TCP
            name: docker-1
        volumeMounts:
          - name: nexus-data
            mountPath: /nexus-data
      volumes:
        - name: nexus-data
          persistentVolumeClaim:
            claimName: nexus
  • Create service to expose nexus UI and docker registry ports
    •                     
apiVersion: v1
kind: Service
metadata:
  name: nexus
  namespace: nexus
  labels:
    app: nexus
spec:
  type: LoadBalancer
  ports:
    - name: nexus-ui
      port: 8081
      protocol: TCP
      targetPort: 8081
    - name: docker-1
      port: 8082
      protocol: TCP
      targetPort: 8082
  selector:
    app: nexus

Verify all resources status

                    
kubectl get ns
kubectl get sc -n nexus
kubectl get pvc -n nexus
kubectl get pv -n nexus
kubectl get po -n nexus
kubectl get svc -n nexus
Labels:

Comments

Post a Comment

Popular posts from this blog

Install AWS CLI on Ubuntu localhost using Ansible Playbook

Install AWS CLI on Ubuntu localhost using Ansible Playbook --- - hosts: localhost tasks: - name: Installing Unzip package package: name: unzip state: present when: ansible_facts['os_family'] == "Debian" become: true - name: Create awscli directory in home directory file: path: ~/awscli state: directory mode: '0755' - name: Download bundled installer zip file get_url: url: https://s3.amazonaws.com/aws-cli/awscli-bundle.zip dest: ~/awscli/awscli-bundle.zip - name: Extract zip file unarchive: src: ~/awscli/awscli-bundle.zip dest: ~/awscli - name: Run install command shell: /home/ubuntu/awscli/awscli-bundle/install -i /usr/local/aws -b /usr/local/bin/aws become: true Same script is also avail...
Post a Comment
Read more

How to clone Github repository using SSH

Run ssh-keygen Upload ssh public key to github account curl -u "gitUsername:password" --data '{"title":"keyName","key":"'"$(cat ~/.ssh/id_rsa.pub)"'"}' https://api.github.com/user/keys Sample output of ssh public key upload command { "id": 1234567890, "key": "ssh-rsa aaaaaaaaaaaaaaaaaaaa/dddd/+aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa", "url": "https://api.github.com/user/keys/123456...
Post a Comment
Read more

Docker Networks

Docker Networks One of the reasons Docker containers and services are so powerful is that you can connect them together, or connect them to non-Docker workloads. Docker’s networking subsystem is pluggable, using drivers. Several drivers exist by default, and provide core networking functionality: Bridge: The default network driver. If you don’t specify a driver, this is the type of network you are creating. Bridge networks are usually used when your applications run in standalone containers that need to communicate. Host: For standalone containers, remove network isolation between the container and the Docker host, and use the host’s networking directly. host is only available for swarm services on Docker 17.06 and higher. See use the host network. Overlay: Overlay networks connect multiple Docker...
Post a Comment
Read more