TechZoneIV

Mapping from dockercli to crictl  crictl  is a command-line interface for  CRI -compatible container runtimes. You can use it to inspect and debug container runtimes and applications on a Kubernetes node.  crictl  and its source are hosted in the  cri-tools  repository. This page provides a reference for mapping common commands for the  docker  command-line tool into the equivalent commands for  crictl . Mapping from docker CLI to crictl The exact versions for the mapping table are for  docker  CLI v1.40 and  crictl  v1.19.0. This list is not exhaustive. For example, it doesn't include experimental  docker  CLI commands. Note:  The output format of  crictl  is similar to  docker  CLI, despite some missing columns for some CLI. Make sure to check output for the specific command if your command output is being parsed programmatically. Retrieve debugging information docker cli crictl De...

  Change the trust settings of a certificate in Keychain Access on Mac In the Keychain Access app   on your Mac, select a keychain from one of the keychains lists, then double-click a certificate. Next to Trust, click the arrow   to display the trust policies for the certificate. To override the trust policies, choose new trust settings from the pop-up menus.

  Rsyslog   is a powerful, secure and high-performance log processing system which accepts data from different types of source (systems/applications) and outputs it into multiple formats Centralized Logging System It has evolved from a regular  syslog  daemon to a fully-featured, enterprise level logging system. It is designed in a client/server model, therefore it can be configured as a client and/or as a central logging server for other servers, network devices, and remote applications. By Default system accept the logs only generated from local host. In this example we will configure a log server and will accept logs from client side. For  t he purpose of Example, we will use the following hosts: Active Server : 10.194.168.128 ;  Hostname : syslog-server-1 Passive Server : 10.194.168.129 ;  Hostname : syslog-server-2 Client1  : 10.194.168.163 ;  Hostname : syslog-server-3 Client2  : 10.194.168.164 ;  Hostname : syslog-server-4 ST...

  Login to Rancher and   Choose project from top menu in selected Cluster wherever you want to deploy the service (In my case in default project want to deploy the service) Click on Deploy Button 1.   Fill up the field details are as below Name of workload: any Scalable deployment of: no of pod want to deploy Dockers Image : Docker Image path (from private or public Registry Server) Namespace:  Default (Choose Accordingly) Choose L4 load balancer as a service from Drop down Publish the container port: Where the service will run under container On listening port: Host port which will be available As  s hown in below image Fill above form accordingly Now Click on launch button Workloads has been created and now running on 80 port. Click on created workload default page of nginx will open.As shown in below image Click on 80/tcp link

  Login to Rancher and  Choose project from top menu in selected Cluster wherever you want to deploy the service (In my case in default project want to deploy the service) 2.   Fill up the field details are as below Name of workload: any Scalable deployment of: no of pod want to deploy Dockers Image : Docker Image path (From private or public registry server) Namespace:  Default (Choose Accordingly) Choose CLUSTER IP as a service from Drop down (L7 Load Balancer) Publish the container port: Where the service will run under container On listening port: Host port which will be available As given below image: 3. So GOTO Load Balancer from top menu and create Ingress service named medium As shown in below image 4.  Fill  u p the field details are as below Namespace : Default (Choose Accordingly) RULES: if select first option then Rancher will generate any random host name otherwise choose specify hostname to use and give any host name Path: where is the...