compiler:compile – the compile goal from the compiler plugin is bound to the compile phase
compiler:testCompile is bound to the test-compile phase
surefire:test is bound to test phase
install:install is bound to install phase
jar:jar and war:war is bound to package phase

What are the Ports being used in Artifactory and why? Create a table and describe it.

8081 for Artifactory
8040 and 8045 for Access
8048 and 9092 for the Replicator
8070 for Web
8086 for Metadata
8082, 8046, 8047, 8049, and 8091 for the Router
8061, and 8062 for Events

8080 for Mission Control Server
8085 for Scheduler
8087 for Executor
(Obsolete from Mission Control version 4.5 and above)
8087 for Insights 
9200 for Elasticsearch (if bundled)
5432 for PostgreSQL (if bundled)
8082, 8046, 8047 and 8049 for the Router

8080 for the Distribution Server
8082, 8046, 8047 and 8049 for the Router
6379 for Redis
5432 for PostgreSQL (if bundled)

8082 for Pipelines API
30001 for Pipelines WWW (UI)
22 for SSH access to the instance
5432 for Database (PostgreSQL) access
30200 for RabbitMQ
30201 for RabbitMQ Admin
30100 for Vault
6379, 16379, 6380, 16380, 6381, 16381 for Redis Cluster

8000 for Xray Server
7000 for Analysis
7002 for Indexer
7003 for Persist
8082, 8046, 8047 and 8049 for the Router
5671, 5672 and 15672 for RabbitMQ
5432 for PostgreSQL (if bundled)

Find out which maven goal help you to upload a artifact?

mvn deploy

Find out which gradle tasks help you to upload a artifact?

gradle : Task :artifactoryPublish

List out top 15 commands in Vmware Tanzu Application service aka PCF.

cf push
cf delete
cf rename

cf help
cf logs
cf scale
cf orgs
cf create-domain
cf routes
cf create-user
cf create-service
cf rename-service
cf delete-service
cf update-service
cf bind-service

It has one or more containers
It’s your application or service
It’s the most basic unit of work
Unit of scheduling
Ephemeral – no POD is ever “redeployed”
Atomicity – They are there or NOT
PODS can communicate through network.
POD get an IP address by kube-proxy
Load balance connects to POD’s as POD have IP address NOT containers
POD is running until we have containers are running inside it
All containers in POD have the same environment like NET, MNT, IPC …

Automated Scheduling
Self-Healing Capabilities
Automated rollouts & rollback
Horizontal Scaling & Load Balancing
Offers environment consistency for development, testing, and production
Infrastructure is loosely coupled to each component can act as a separate unit
Provides a higher density of resource utilization
Offers enterprise-ready features
Application-centric management
Auto-scalable infrastructure
You can create predictable infrastructure

How kubernetes works?

Kubernetes is the Linux kernel which is used for distributed systems. It helps you to be abstract the underlying hardware of the nodes(servers) and offers a consistent interface for applications that consume the shared pool of resources

What are the components of Master? explain in one line sentense

Master Node
The master node is the first and most vital component which is responsible for the management of Kubernetes cluster. It is the entry point for all kind of administrative tasks. There might be more than one master node in the cluster to check for fault tolerance.

The master node has various components like API Server, Controller Manager, Scheduler, and ETCD. Let see all of them.

API Server: The API server acts as an entry point for all the REST commands used for controlling the cluster.

Scheduler
The scheduler schedules the tasks to the slave node. It stores the resource usage information for every slave node. It is responsible for distributing the workload.

It also helps you to track how the working load is used on cluster nodes. It helps you to place the workload on resources which are available and accept the workload.

Etcd
etcd components store configuration detail and wright values. It communicates with the most component to receive commands and work. It also manages network rules and port forwarding activity.

Worker/Slave nodes
Worker nodes are another essential component which contains all the required services to manage the networking between the containers, communicate with the master node, which allows you to assign resources to the scheduled containers.

Kubelet: gets the configuration of a Pod from the API server and ensures that the described containers are up and running.
Docker Container: Docker container runs on each of the worker nodes, which runs the configured pods
Kube-proxy: Kube-proxy acts as a load balancer and network proxy to perform service on a single worker node
Pods: A pod is a combination of single or multiple containers that logically run together on nodes

What are the components of Worker/Node/Agent

Docker:
Docker which helps in running the encapsulated application containers in a relatively isolated but lightweight operating environment.

Kubelet Service:
responsible for relaying information to and from control plane service. It interacts with etcd store to read configuration details and wright values. This communicates with the master component to receive commands and work. The kubelet process then assumes responsibility for maintaining the state of work and the node server. It manages network rules, port forwarding, etc.

Kubernetes Proxy Service:
runs on each node and helps in making services available to the external host. It helps in forwarding the request to correct containers and is capable of performing primitive load balancing. It makes sure that the networking environment is predictable and accessible and at the same time it is isolated as well. It manages pods on node, volumes, secrets, creating new containers’ health checkup, etc.

What are the components of Workstation?

kubectl ,JSON

sudo yum install -y yum-utilssudo yum install -y yum-utils device-mapper-persistent-data lvm2
sudo yum-config-manager --add-repo https://download.docker.com/linux/centos/docker-ce.repo
sudo yum install –y https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
sudo yum-config-manager --enable rhui-REGION-rhel-server-extras
sudo yum install -y docker-ce
docker -v
clear
sudo systemctl enable docker
sudo systemctl start docker
clear
docker info

Step 4 – Assignment#1

docker ps -a  
docker exec -it 5276bae5464e bash
apt-get -y update
apt-get -y install git
apt-get install apache2

docker exec 5276bae5464e git

Step 5 – Assignment#2

docker run -d -p 8080:80 httpd
curl http://192.168.2.16:8080/