Real Time Scenario Based Interview Questions

OpenShift simplifies application deployment and management with its Kubernetes-based platform, offering
automation and security features. Developers can focus on coding, supported by built-in CI/CD pipelines. Its
scalability and flexibility make it ideal for diverse use cases, from microservices to enterprise applications. OpenShift
offers monitoring and logging tools for efficient troubleshooting and supports multi-cloud environments for added
flexibility.

1. Differences between OpenShift and Kubernetes and how OpenShift boosts developer efficiency?

Ans:

OpenShift, developed by Red Hat, is a containerization platform that utilizes Docker containers and Kubernetes
orchestration. While Kubernetes primarily focuses on container management, OpenShift extends its capabilities by
integrating developer tools, automated workflows, and enhanced security features to boost developer productivity. It
also provides a unified platform for both development and operations teams, streamlining the development lifecycle
and deployment processes.

2. Explain the architectural elements of OpenShift and how they deviate from a typical Kubernetes setup.

Ans:

OpenShift’s architecture mirrors Kubernetes but incorporates additional components by Red Hat. It operates on a
master-slave structure, where the controller node oversees cluster orchestration and management while multiple
worker nodes host application containers. Additionally, OpenShift includes built-in tools for continuous integration and
deployment, enhancing the automation of the software delivery pipeline. Its security enhancements, such as
integrated authentication and authorization.

3. OpenShift comprises essential components:

Ans:

 Controller Node: Governs cluster orchestration, including scheduling, scaling, and monitoring applications.
 Node (Worker Node): Hosts application containers and executes tasks assigned by the controller node.
 Etc: A distributed key-value store for storing cluster configuration and state information.
 API Server: Facilitates communication between cluster components and external clients.
 Controller Manager: Manages controllers responsible for maintaining the cluster’s desired state.
 Scheduler: Assigns workloads to worker nodes based on resource availability.

4. Describe the structure of pods in OpenShift and their importance in the deployment process.

Ans:
 Pods in OpenShift represent the smallest deployable units. They comprise one or more containers sharing a network
namespace and storage volumes. Managed by the Kubernetes runtime, pods can contain multiple tightly coupled
containers for collaborative operations.

5. OpenShift enhances Kubernetes for easier development and deployment?

Ans:

OpenShift leverages Kubernetes for container orchestration, employing its features for scheduling, scaling, and
management while offering additional tools and functionalities to streamline development and deployment processes.

6. What are node roles in OpenShift, and how do they support container apps?

Ans:

 Nodes in OpenShift are worker machines hosting application containers.

 Each node runs a Kubelet agent, communicating with the controller node and executing assigned tasks.
 Nodes provide computing resources for containerized applications and manage their operations.

7. Why is etcd crucial in OpenShift, and how does it ensure uniformity and dependability across the cluster?

Ans:

 Centralized Data Storage: etcd maintains a centralized repository of configuration and state data, ensuring that all
nodes in the cluster have a consistent view of the system’s state.
 Consistency and Reliability: It uses the Raft consensus algorithm to ensure that data changes are replicated across
all etcd nodes in a reliable and consistent manner, even in the face of network partitions or node failures.
 Configuration Management: etcd stores Kubernetes and OpenShift configurations, such as pod specifications and
service definitions, allowing for uniform application deployment and management across the cluster.
 Failover and Recovery: In case of node failures, etcd’s replication and leader election mechanisms help maintain
data integrity and cluster availability, facilitating quick recovery and minimal disruption.

8. How does OpenShift manage container networking, and what are its key features?

Ans:

OpenShift manages networking for containerized applications using the Kubernetes networking model. It facilitates
communication between containers within the cluster and exposes services to external clients, supporting various
networking plugins and configurations to suit diverse requirements. Additionally, OpenShift provides features like
service discovery, load balancing, and network policies to enhance application connectivity and security.

9. Describe the difference between OpenShift Origin and OpenShift Container Platform.

Ans:

Feature OpenShift Origin OpenShift Container Platform

Development Open-source upstream project for Enterprise-ready version for production use
Environment experimentation
Stability May include bleeding-edge features Offers stability and support for production
Support Community-driven support Official support and additional enterprise
features
Deployment Suitable for experimentation and Designed for enterprise-grade deployments
 development
Innovation Foundation for innovation Provides reliability and support for
enterprises
10. OpenShift supports various deployment strategies:

Ans:

 Rolling Deployment: This deployment method gradually applies updates to the application, ensuring zero downtime
by replacing old instances with new ones incrementally.
 Blue-Green Deployment: This deployment maintains two identical production environments (blue and green), one
serving live traffic while the other is updated. Once updated, traffic shifts to the new environment.
 Canary Deployment: Gradually shifts traffic from the old to the new application version, allowing real-time monitoring
before full deployment.
 A/B Testing: Deploys multiple application versions simultaneously, routing a portion of traffic to each for performance
and user experience comparison.
 Custom Deployment Strategies: OpenShift allows custom strategies tailored to specific application needs and use
cases.

11. OpenShift guarantees application high availability through several methods:

Ans:

 Replication: Application pods are duplicated across multiple worker nodes, ensuring resilience and fault tolerance. If
one node goes down, replicas on other nodes continue serving requests.
 Auto-scaling: OpenShift can automatically adjust the number of application pods based on resource usage metrics,
ensuring optimal capacity to handle varying workloads.
 Node Failover: In the event of node failure, OpenShift promptly reschedules pods on healthy nodes to maintain
application availability.
 Load Balancing: OpenShift’s built-in load balancing capabilities distribute incoming traffic evenly across multiple
instances of application pods, preventing any single pod or node from becoming overloaded.
 Health Checks: OpenShift continuously monitors the health of application pods and nodes, promptly restarting or
rescheduling unhealthy pods to uphold overall system health.

12. Explain the concept of projects in OpenShift?

Ans:

In OpenShift, projects serve as organizational units for resources within a cluster. Each project acts as a distinct
namespace, enabling teams or individuals to maintain their isolated environments for developing, deploying, and
managing applications. Projects regulate resource access, facilitating secure collaboration while preserving
segregation of responsibilities.

13. What is an ImageStream, and how does it relate to OpenShift?

Ans:

An ImageStream within OpenShift is a Kubernetes construct used for overseeing and tracking alterations to container
images. It serves as a central repository for storing and versioning container images utilized by applications deployed
in the cluster. ImageStreams empower OpenShift to automatically detect and instigate updates when new images
become available, streamlining continuous integration and deployment workflows.
 14. The process of deploying applications in OpenShift entails the following stages:

Ans:

 Define Application Configuration: Specify the desired state of the application, encompassing container image,
resource requisites, networking, and storage.
 Establish Deployment Configuration: Outline the application’s deployment specifics, including replica count,
update methodology, and deployment triggers.
 Deploy Application: OpenShift creates and manages essential resources (pods, services, routes) to deploy the
application according to the stipulated configuration.
 Monitor Application Health: Continuously monitor the health status of application pods and services, automatically
initiating restarts or scaling adjustments as necessary to ensure sustained availability and performance.

15. What role does BuildConfig play in OpenShift’s deployment process?

Ans:

BuildConfig in OpenShift outlines the build configuration for source code repositories, dictating how to construct
container images from source code. It encompasses parameters such as source code location, build strategy
(source-to-image, Dockerfile, custom scripts), and output image repository. BuildConfig plays a pivotal role in the
deployment workflow by automating the build and packaging of application code into container images prior to
deployment.

16. Describe the function of Templates in OpenShift.

Ans:

OpenShift templates offer pre-configured setups for deploying applications and services. They encapsulate best
practices and recommended configurations for various application types, simplifying the creation of consistent
deployments. Templates incorporate customizable parameters during deployment, empowering users to tailor
deployments to their specific needs without the need for manual configuration of each component.

17. How does OpenShift manage storage for containerized applications?

Ans:

 OpenShift manages storage for containerized applications through Persistent Volume (PV) and Persistent Volume
Claim (PVC) resources.
 PVCs delineate storage requirements for applications, while PVs represent actual storage volumes provisioned by
administrators.
 OpenShift dynamically provisions and attaches storage volumes to application pods based on PVC specifications,
ensuring persistent data availability across container restarts and rescheduling.

18. What is the role of the Registry in OpenShift?

Ans:

The Registry in OpenShift serves as a centralized repository for storing container images employed by applications
within the cluster. It furnishes a secure and scalable storage solution for container images, facilitating efficient
application distribution and deployment. The Registry seamlessly integrates with OpenShift’s build and deployment
processes, automatically fetching and pushing images as necessary during application lifecycle management.
 19. Explain how OpenShift supports CI/CD pipelines.

Ans:

OpenShift facilitates Continuous Integration/Continuous Deployment (CI/CD) pipelines by integrating with tools such
as Jenkins, GitLab, or Tekton. CI/CD pipelines automate the build, testing, and deployment processes, enabling swift
and reliable delivery of changes to production environments. OpenShift provides capabilities for defining and
orchestrating CI/CD workflows, including integration with source code repositories, automated testing, and diverse
deployment strategies.

20. OpenShift manages application scaling through horizontal and vertical scaling methods:

Ans:

 Horizontal Scaling: OpenShift dynamically adjusts the number of application pods horizontally by scaling the
number of replicas based on resource usage metrics like CPU and memory utilization. This ensures adequate
capacity to handle workload fluctuations without manual intervention.
 Vertical Scaling: OpenShift supports vertical scaling, enabling individual pods to scale up or down by modifying their
resource limits and requests. This allows applications to efficiently utilize available resources and meet performance
demands as workload characteristics evolve.

Subscribe For Free Demo

Subscribe

21. What security features are available in OpenShift?

Ans:

 OpenShift offers various security features such as role-based access control (RBAC), network policies, pod security
policies, and image scanning for vulnerabilities.
 RBAC ensures that only authorized users have access to resources, while network policies control traffic flow
between pods.
 Pod security policies enforce security standards for pods, and image scanning identifies and addresses security
vulnerabilities in container images.

22. How does OpenShift manage authentication and authorization?

Ans:

OpenShift manages authentication through identity providers (IdPs) such as LDAP, OAuth, and Active Directory,
allowing users to log in using their existing credentials. Authorization is handled through role-based access control
(RBAC), which defines permissions for users and groups based on their roles within the cluster. Additionally,
OpenShift provides fine-grained control with project and resource-specific permissions, enhancing security and
compliance.
 23. Describe the role of Operators in OpenShift.

Ans:

Operators in OpenShift automate the management of complex applications and services by encapsulating
operational knowledge in software. They use custom controllers to continuously monitor and manage the state of
applications, ensuring they meet desired configurations and respond to changes automatically. Operators also handle
tasks such as scaling, backups, and updates, reducing manual intervention and enhancing operational efficiency.

24. What is the Operator Framework, and how does it function in OpenShift?

Ans:

 The Operator Framework is a toolkit for building Kubernetes-native applications, including Operators.
 In OpenShift, Operators leverage the Operator Framework to automate the deployment, management, and scaling of
applications.
 They use custom resource definitions (CRDs) to define custom resources and controllers to reconcile the desired
state with the current state of these resources.

25. Explain the purpose of Custom Resource Definitions (CRDs) in OpenShift.

Ans:

The Kubernetes API is extended by specialized Resource Definitions (CRDs) in OpenShift to support specialized
resources unique to platform-running applications. They let users develop and manage resources beyond what
Kubernetes comes with by default by defining custom objects and their properties. By allowing the creation of unique
controllers and operators to automate the management of various resources, CRDs increase the extensibility and
flexibility of the platform.

26. How does OpenShift integrate with monitoring and logging solutions?

Ans:

OpenShift integrates with monitoring solutions such as Prometheus and logging solutions like Elasticsearch and
Fluentd. Prometheus provides monitoring and alerting capabilities, while Elasticsearch and Fluentd offer log
aggregation and analysis. These integrations allow administrators to monitor the health and performance of
OpenShift clusters and applications.

27. What is the OpenShift Container Storage (OCS) platform?

Ans:

 The OpenShift Container Storage (OCS) platform provides persistent storage for containerized applications running
on OpenShift.
 It integrates with Kubernetes and OpenShift to provide scalable, distributed storage solutions using technologies such
as Ceph and Rook.
 OCS offers features such as dynamic provisioning, data replication, and data encryption to ensure data availability
and integrity.

28. How are OpenShift clusters upgraded?

 Ans:

OpenShift clusters are upgraded using a rolling update strategy, where nodes are updated one at a time to minimize
downtime. Administrators can use the built-in upgrade tools provided by OpenShift, such as the oc command-line
interface (CLI) or the web console, to initiate and manage cluster upgrades. Before upgrading, administrators should
review release notes and perform backups to ensure a smooth upgrade process.

29. What authentication methods does OpenShift support?

Ans:

OpenShift supports various authentication methods, including password-based authentication, token-based

authentication, LDAP, OAuth, and Active Directory. Users can choose the authentication method that best suits their
environment and integrate it with existing identity providers for seamless user authentication. Additionally, OpenShift
allows for fine-grained access control by leveraging these authentication methods, ensuring secure and manageable
user access across the platform.

30. How does OpenShift manage resource allocation?

Ans:

 OpenShift manages resource allocation using Kubernetes-native features such as resource requests, limits, and
quotas.
 Resource requests define the minimum amount of CPU and memory required by a container, while limits specify the
maximum amount of resources a container can use.
 Quotas enforce resource limits at the namespace level, ensuring fair resource allocation among users and
applications.

31. Describe the functionality of the OpenShift web console.

Ans:

The OpenShift web console is a graphical user interface for managing and monitoring OpenShift clusters. It allows
users to deploy, manage, and scale applications, as well as monitor cluster health and performance. Users can also
access logs, metrics, and configuration settings through the web console, providing a centralized platform for cluster
administration.

32. What are the best practices for securing OpenShift clusters?

Ans:

 Implementing role-based access control (RBAC).

 Enabling network policies.
 Regularly updating and patching the system.
 Monitoring for security threats and vulnerabilities.
 Enabling encryption for data in transit and at rest.

33. Explain the concept of namespaces in OpenShift.

Ans:
 Namespaces in OpenShift divide cluster resources into virtual clusters. They enable multi-tenancy by allowing
multiple users or teams to share a single physical cluster while maintaining isolation. Each namespace has its own
set of resources, such as pods, services, and storage, and can apply its own policies and resource quotas.

34. How does OpenShift handle application updates and rollbacks?

Ans:

 OpenShift handles application updates by using deployment configurations and rolling updates.
 When a new version of an application is deployed, OpenShift gradually replaces the old version with the new one,
ensuring minimal downtime.
 If an update causes issues, OpenShift supports rollbacks by reverting to a previous known-good version of the
application.

35. What is the role of the OpenShift Service Mesh?

Ans:

 The OpenShift Service Mesh provides a dedicated infrastructure layer for managing service-to-service
communication within an OpenShift cluster.
 It offers features such as traffic management, security, observability, and policy enforcement, enabling developers to
build and deploy microservices-based applications more efficiently.

36. How are applications troubleshooted in OpenShift?

Ans:

Applications in OpenShift can be troubleshooted using various built-in tools and features such as logging, monitoring,
and debugging capabilities. OpenShift provides access to logs, metrics, and events through the web console or
command-line interface, allowing administrators to identify and diagnose issues affecting applications. Additionally,
OpenShift integrates with external monitoring and logging solutions, providing advanced analytics and alerting for
proactive issue management.

37. How does OpenShift handle node failures?

Ans:

OpenShift employs a combination of strategies to handle node failures, including automatic failover and self-healing
mechanisms. When a node fails, OpenShift automatically redistributes workloads to healthy nodes and spins up new
instances of pods to maintain application availability. Additionally, administrators can configure node monitoring and
alerts to proactively address issues. The platform also supports rolling updates and automated rollbacks to ensure
minimal disruption during maintenance or failures.

38. What is the Operator Lifecycle Manager (OLM) in OpenShift?

Ans:

The Operator Lifecycle Manager (OLM) is an OpenShift component that facilitates the management and lifecycle of
Kubernetes operators. OLM helps users discover, install, manage, and upgrade operators, which are applications-
specific controllers that extend OpenShift’s functionality by automating complex operational tasks. It provides a user-
 friendly interface for managing operator subscriptions and updates, and ensures that operators are running in a
consistent and supported state across the cluster.

39. Explain the purpose of network policies in OpenShift.

Ans:

Network policies in OpenShift define rules for controlling inbound and outbound network traffic to and from pods
within a namespace. They provide a way to enforce security and segmentation by specifying which pods are allowed
to communicate with each other and which network protocols and ports are permitted. These policies help prevent
unauthorized access and reduce the risk of lateral movement within the cluster, enhancing overall network security
and compliance.

40. How does OpenShift support multi-tenancy?

Ans:

OpenShift supports multi-tenancy by using namespaces to create virtual clusters within a single physical cluster.
Each namespace isolates resources and configurations, allowing multiple users or teams to share the same cluster
while maintaining separation and security. Additionally, OpenShift provides role-based access control (RBAC) to
manage permissions and access rights across namespaces.

Get JOB OpenShift Training for Beginners By MNC Experts

 Instructor-led Sessions

 Real-life Case Studies

 Assignments
Explore Curriculum
41. Describe the role of Operators in managing applications.

Ans:

 Operators automate the management of applications in OpenShift by encoding operational knowledge into software.
 They monitor, maintain, and update applications based on predefined policies and best practices.
 Operators ensure application health, perform scaling, and handle upgrades seamlessly, reducing manual
intervention.
 By using custom resources and controllers, Operators streamline application lifecycle management, improving
efficiency.
 They enable self-healing capabilities, detect and resolve issues proactively, and optimize resource utilization.

42. What are the different types of routes in OpenShift?

Ans:

 OpenShift offers two main types of routes: Edge and Re-encrypt.

 Edge routes terminate SSL/TLS traffic at the router, suitable for most HTTP/HTTPS traffic.
 Re-encrypt routes terminate SSL/TLS traffic at the router and then re-encrypt it before forwarding it to backend pods.
 Both route types provide secure access to applications running in OpenShift clusters.
 Edge routes are commonly used for public-facing applications, while re-encrypt routes add an extra layer of security
for internal communication.

43. How are security patches and updates managed in OpenShift?

Ans:

 OpenShift manages security patches and updates through its integrated update mechanism, ensuring the platform
remains secure.
 Red Hat releases regular updates to address vulnerabilities and improve system stability.
 OpenShift administrators can schedule updates during maintenance windows to minimize disruptions.
 Automated update processes streamline the deployment of patches across clusters, reducing manual effort.
 Prior to applying updates, administrators can review release notes and conduct testing in staging environments.

44. What is the OpenShift Container Platform (OCP)?

Ans:

The OpenShift Container Platform (OCP) is a comprehensive enterprise Kubernetes platform developed by Red Hat.
It provides a scalable and secure container orchestration solution for deploying and managing applications. OCP
includes features such as automated operations, built-in monitoring, and integrated security controls. It supports
hybrid and multi-cloud environments, enabling consistent application deployment across infrastructure.

45. How does OpenShift handle container networking across clusters?

Ans:

OpenShift uses the Kubernetes networking model for container networking across clusters. Each cluster has its
network overlay for pod-to-pod communication within the cluster. To enable communication between pods across
clusters, OpenShift implements network policies and service discovery mechanisms. Multi-cluster deployments may
utilize technologies like Kubernetes Federation or Service Mesh for cross-cluster communication.

46. What storage options are available in OpenShift?

Ans:

 OpenShift provides various storage options to meet diverse application requirements.

 Persistent Volume (PV) and Persistent Volume Claim (PVC) enable persistent storage for stateful applications.
 Storage classes allow dynamic provisioning of storage resources based on workload demands.
 OpenShift supports storage solutions such as NFS, GlusterFS, Ceph, Amazon EBS, and Azure Disk.
 Container-native storage solutions, like OpenShift Container Storage (OCS), offer scalable and resilient storage for
cloud-native applications.

47. What is the OpenShift Serverless platform?

Ans:

 The OpenShift Serverless platform provides a serverless computing environment for running event-driven workloads.
 It abstracts infrastructure management, allowing developers to focus on writing code without worrying about server
provisioning or scaling.
 OpenShift Serverless is based on the Knative project and provides features like auto-scaling, event sources, and
request-driven scaling.
 Developers can deploy functions or applications as serverless workloads, which automatically scale up or down
based on demand.

48. How does OpenShift handle pod eviction?

Ans:

 OpenShift handles pod eviction to ensure resource availability and maintain cluster stability.
 Pod eviction occurs when nodes experience resource pressure or when node maintenance activities are performed.
 Kubernetes eviction policies prioritize pods based on factors like QoS class, resource requests, and pod disruption
budgets.
 Pods with lower priority, such as best-effort pods, are evicted first to reclaim resources for higher-priority workloads.
 OpenShift provides mechanisms for configuring eviction thresholds and policies to control pod eviction behavior.

49. Describe the role of the OpenShift Ansible Broker.

Ans:

The OpenShift Ansible Broker automates application lifecycle management by integrating Ansible playbooks with
OpenShift. It allows developers to define application operations using Ansible, enabling tasks like provisioning,
deployment, and scaling. The broker acts as a bridge between OpenShift and Ansible, facilitating seamless
automation of complex workflows. Through Ansible roles and modules, it streamlines repetitive tasks and ensures
consistency in application management within OpenShift environments.

50. What is cluster auto-scaling in OpenShift?

Ans:

Cluster auto-scaling in OpenShift dynamically adjusts the size of the cluster based on resource demand. It
automatically adds or removes nodes to maintain optimal performance and resource utilization. By monitoring metrics
such as CPU and memory usage, OpenShift can scale the cluster up during peak loads and scale it down during
periods of low activity. This elasticity ensures efficient resource use and improves application availability without
manual intervention.

51. How are configuration changes managed in OpenShift?

 Ans:

In OpenShift, configuration changes are managed through ConfigMaps and Secrets, which store configuration data
separately from the application code. These configurations can be updated dynamically without redeploying
applications, ensuring flexibility and efficiency in managing configurations across clusters. Additionally, ConfigMaps
and Secrets allow for centralized configuration management and secure handling of sensitive information, reducing
the risk of configuration errors and enhancing operational control.

52. Explain the role of Operators in automating application management.

Ans:

 Operators in OpenShift automate application management by using custom controllers to observe and manage
resources, such as deploying, scaling, and updating applications.
 They enable automated operations based on predefined logic, reducing manual intervention and improving
consistency and reliability in application management.

53. What is immutable infrastructure, and how is it applied in OpenShift?

Ans:

 Immutable infrastructure refers to infrastructure that, once deployed, cannot be modified.

 In OpenShift, this concept is applied by using container images and declarative configurations to create consistent
and reproducible environments.
 Any changes result in new deployments, ensuring consistency and reliability in application environments.

54. How does OpenShift handle node scheduling?

Ans:

OpenShift handles node scheduling through Kubernetes’ built-in scheduler, which assigns pods to nodes based on
resource requirements and constraints. The scheduler considers factors such as available resources, affinity, and
anti-affinity rules to optimize resource allocation and maintain cluster stability. Additionally, it takes into account taints
and tolerations to ensure that pods are scheduled only on nodes that can meet their specific needs.

55. Describe the functionality of the OpenShift Developer Console.

Ans:

The OpenShift Developer Console provides a web-based interface for developers to interact with OpenShift clusters.
It offers features such as project management, application deployment, monitoring, and troubleshooting tools,
simplifying the development and deployment of applications on OpenShift. Additionally, it provides integrated support
for CI/CD pipelines and collaborative features to streamline team workflows and accelerate development cycles.

56. What is the OpenShift Operator SDK?

Ans:

The OpenShift Operator SDK is a toolkit for building Kubernetes Operators, which are applications that automate the
management of complex, stateful workloads on Kubernetes and OpenShift. The SDK provides frameworks, libraries,
 and tools to streamline the development, testing, and deployment of Operators, enabling efficient application
management automation.

57. How do admission controllers work in OpenShift?

Ans:

 Admission controllers in OpenShift are plugins that intercept requests to the Kubernetes API server before they are
persisted to the cluster.
 They enforce policies and security controls by validating and mutating requests based on predefined rules, helping
ensure compliance, security, and consistency in cluster operations.

58. What is the purpose of the OpenShift Router?

Ans:

 The purpose of the OpenShift Router is to route incoming traffic to the appropriate services within an OpenShift
cluster.
 It acts as a load balancer, distributing traffic to pods based on routing rules defined in the cluster’s routes.
 This enables external access to applications running in the cluster while maintaining security and scalability.

59. How does OpenShift handle image scanning for vulnerabilities?

Ans:

OpenShift handles image scanning for vulnerabilities by integrating with container scanning tools such as Clair or
Quay Security Scanner. These tools analyze container images for known security vulnerabilities and provide reports
to administrators, enabling them to take appropriate actions to mitigate risks and ensure the security of deployed
applications.

60. Explain the concepts of affinity and anti-affinity in OpenShift.

Ans:

In OpenShift, affinity and anti-affinity are concepts used to influence pod placement decisions during scheduling.
Affinity rules specify preferences for pod placement based on node attributes or labels, while anti-affinity rules specify
constraints to avoid placing pods on the same node. These rules help optimize resource utilization, improve
performance, and enhance availability and resilience in OpenShift clusters.
 Develop Your Skills with OpenShift Certification Training

Weekday / Weekend BatchesSee Batch Details

61. What are the best practices for managing secrets in OpenShift?

Ans:

 Encrypt secrets at rest and in transit.

 Limit access to secrets based on roles.
 Rotate secrets regularly to enhance security.
 Avoid hardcoding secrets in application code.
 Utilize built-in OpenShift tools for secret management.
 Regularly audit and monitor access to secrets.

62. Describe the role of the OpenShift Container Network Interface (CNI).

Ans:

 The OpenShift CNI manages networking for pods.

 It assigns IP addresses and routes traffic.
 Ensures communication between pods and external networks.
 Supports various network plugins for flexibility.
 Enables secure and efficient communication within the cluster.
 Facilitates seamless integration with external networking solutions.

63. How does OpenShift manage application authentication and authorization?

Ans:

 Utilizes integrated authentication mechanisms like OAuth.

 Integrates with external identity providers for authentication.
 Implements role-based access control (RBAC) for authorization.
 Supports fine-grained access control policies.
 Enables centralized management of user access and permissions.
 Provides auditing capabilities for monitoring access activities.

64. What is the OpenShift Monitoring Operator?

Ans:

Manages monitoring solutions on OpenShift clusters. Automates deployment and configuration of monitoring tools.
Monitors cluster health, performance, and resource usage. Facilitates alerts and notifications for critical events.
Enables visualization of cluster metrics and performance data. Streamlines troubleshooting and optimization of
cluster resources.

65. Explain the concept of custom resource controllers in OpenShift.

Ans:
 Extend Kubernetes functionality to manage custom resources. Define custom resources and their lifecycle.
Implement logic to handle custom resource operations. Enable automation of complex workflows and tasks. Enhance
flexibility and extensibility of OpenShift clusters. Provide a framework for developers to create custom solutions.

66. How are environment variable changes managed in OpenShift?

Ans:

 Environment variables are managed via ConfigMaps and Secrets.

 Updates to ConfigMaps and Secrets trigger redeployment.
 OpenShift automatically injects updated variables into pods.
 Ensures consistency and reliability of environment configurations.
 Supports dynamic updates without disrupting running applications.
 Facilitates efficient management of application configurations.

67. What container runtimes are supported in OpenShift?

Ans:

 OpenShift supports Docker and container runtimes.

 It provides flexibility in choosing the preferred runtime.
 Ensures compatibility with existing containerized applications.
 Enables seamless migration of workloads across environments.
 Offers support for various container image formats.
 Integrates with container runtime security features.

68. Describe the functionality of the OpenShift Service Catalog.

Ans:

 Acts as a centralized repository of services and APIs.

 Enables self-service provisioning of services for applications.
 Provides a catalog of predefined service offerings.
 Supports customization and extension of service offerings.
 Facilitates easy discovery and consumption of services.
 Streamlines the deployment and management of microservices architectures.

69. How does OpenShift handle pod networking and IP assignment?

Ans:

OpenShift CNI assigns each pod a unique IP address. Enables communication between pods within the cluster.
Supports network policies for fine-grained control over traffic. Integrates with external networking solutions for
connectivity. Manages pod networking transparently to users. Ensures isolation and security of pod communication
channels.

70. What is the OpenShift Service Mesh Operator?

Ans:
 Manages service mesh deployments on OpenShift clusters. Automates the deployment and configuration of service
mesh components. Facilitates secure and resilient communication between microservices. Enables traffic
management, monitoring, and observability. Integrates with Istio for advanced service mesh capabilities. Streamlines
the implementation of service mesh architecture in OpenShift environments.

71. Explain the concepts of node selectors and node affinity.

Ans:

 Node selectors specify where pods can be scheduled,

 Using labels to match nodes as suitable targets.
 Node affinity enhances this, adding more control,
 Allowing finer-grained rules for pod placement.
 Together, they optimize resource utilization,
 Ensuring efficient distribution across the cluster.

72. How does OpenShift scale applications based on metrics?

Ans:

 OpenShift utilizes Horizontal Pod Autoscalers (HPAs),

 Monitoring specified metrics to trigger scaling events.
 Metrics like CPU usage or custom metrics are observed,
 Scaling pods in or out to meet defined thresholds.
 This automated process maintains application performance,
 Adapting to varying workload demands seamlessly.

73. What deployment hooks does OpenShift support?

Ans:

OpenShift supports lifecycle hooks for deployments, Pre and post-hooks enabling custom actions. These hooks
integrate with deployment processes, Executing scripts or commands at key stages. Useful for tasks like database
migrations or validations, Ensuring smooth and controlled application updates. Additionally, hooks help automate
repetitive tasks and maintain consistency across different environments, reducing the potential for human error during
deployments.

74. Describe the role of the OpenShift Kubernetes API.

Ans:

 The OpenShift Kubernetes API serves as the interface,

 Allowing users to interact with the cluster.
 It provides endpoints for managing resources,
 Like pods, services, deployments, and more.
 Through this API, automation, and integration thrive,
 Enabling seamless orchestration of containerized workloads.
 75. How does OpenShift integrate with external monitoring and logging solutions?

Ans:

OpenShift integrates with external monitoring and logging, Through adapters and plugins for various solutions.
Prometheus and Grafana for monitoring metrics, ELK Stack or Fluentd for centralized logging. These integrations
offer insights into cluster health, Enabling effective troubleshooting and analysis. Additionally, they support
customizable dashboards and alerts, helping teams proactively manage and respond to system issues.

76. What are the core components of OpenShift?

Ans:

 OpenShift’s core components include the Kubernetes runtime,

 Extended with additional features and tooling.
 The Kubernetes API server provides cluster management,
 Etcd ensures reliable data storage and consistency.
 Alongside, controllers and schedulers orchestrate resources,
 Creating a robust platform for containerized applications.

77. How does OpenShift facilitate container orchestration?

Ans:

OpenShift simplifies container orchestration through automation, Managing container lifecycle from deployment to
scaling. It abstracts away complexities with declarative configurations, Handling resource provisioning and scheduling
efficiently. With built-in tools like Kubernetes-native operators, It streamlines operations, ensuring application
reliability.

78. Explain the role of Kubernetes in OpenShift.

Ans:

 Kubernetes forms the foundation of OpenShift,

 Providing container orchestration and management.
 OpenShift builds upon Kubernetes, adding features,
 Such as developer-friendly tools and enterprise-grade security.
 It extends Kubernetes capabilities for enterprise workloads,
 Offering a comprehensive platform for modern application delivery.

79. What deployment strategies does OpenShift support?

Ans:

 OpenShift supports various deployment strategies,

 Including rolling, blue-green, and canary deployments.
 Rolling updates ensure zero downtime during updates,
 While blue-green deployments enable seamless switching.
 Canary deployments test new versions with a subset of users,
 Providing risk mitigation before full release.

80. How does OpenShift handle container networking?

Ans:

OpenShift manages container networking through SDN, Providing communication between pods and services. It
abstracts network configurations, simplifying setup, While ensuring isolation and security between workloads. Using
plugins like Multus, it supports multiple network interfaces, Adapting to diverse networking requirements seamlessly.
OpenShift Sample Resumes! Download & Edit, Get Noticed by Top Employers!DOWNLOAD

81. What role do routes play in OpenShift, and how do they enable external access to cluster services?

Ans:

Routes in OpenShift enable external access to services within the cluster. They act as HTTP/HTTPS proxies,
directing traffic from external clients to the appropriate services based on hostname and path. Routes offer
developers a means to expose applications externally without revealing internal details. They also offer features like
load balancing, which may be set up to distribute traffic among service instances efficiently, and TLS termination for
secure connections.

82. How does OpenShift ensure high availability of applications?

Ans:

OpenShift utilizes replication controllers to ensure multiple application instances are running across the cluster. It
automatically detects failed instances and restarts them on healthy nodes. Load balancing distributes traffic evenly
across healthy instances to prevent overloading. OpenShift supports horizontal scaling, dynamically adjusting the
number of instances based on demand. It employs health checks to monitor application status and trigger actions in
case of failures.

83. What storage options does OpenShift provide for persistent data?

Ans:

 OpenShift offers various storage options, including PersistentVolumes (PVs) and PersistentVolumeClaims (PVCs).
 PVs can be provisioned from different storage backends such as NFS, GlusterFS, or cloud providers like AWS and
Azure.
 PVCs abstract the underlying storage details from applications, allowing easy management and migration.
 OpenShift supports dynamic provisioning, automatically creating PVs when PVCs are requested.
 It also integrates with Container Storage Interface (CSI) compliant storage providers for flexibility.

84. How are secrets managed in OpenShift?

Ans:

Secrets in OpenShift are stored securely using encryption and access controls. They can be created manually or
generated automatically by the platform. OpenShift provides APIs and tools for managing secrets programmatically.
 Role-based access controls (RBAC) ensure that only authorized users or applications can access secrets. Secrets
can be mounted into containers as files or environment variables during runtime.

85. Explain the concept of builds and image streams in OpenShift.

Ans:

Builds in OpenShift are processes that transform source code into runnable container images. They can be triggered
automatically from source code repositories or initiated manually. OpenShift supports various build strategies,
including Source-to-Image (S2I), Dockerfile, and custom scripts. Image streams track and manage container images
throughout their lifecycle. Image streams enable seamless integration with continuous integration and delivery
(CI/CD) pipelines.

86. What role does the OpenShift CLI (oc) play in managing clusters?

Ans:

 The OpenShift CLI (oc) is a command-line tool for interacting with OpenShift clusters.
 It allows administrators and developers to manage applications, containers, and resources.
 With OC, users can create, deploy, scale, and monitor applications and services.
 It provides access to cluster resources such as pods, deployments, and services.
 The CLI facilitates automation and scripting of common tasks for cluster management.
 It offers functionalities for troubleshooting, debugging, and accessing cluster logs.

87. How does OpenShift handle application scaling?

Ans:

 OpenShift supports both manual and automatic scaling of applications.

 Horizontal scaling adds or removes instances of an application based on demand.
 Vertical scaling adjusts the resources allocated to individual application instances.
 Autoscaling automatically adjusts the number of replicas based on metrics like CPU or memory usage.
 Users can define custom scaling policies and thresholds for precise control.
 OpenShift provides monitoring capabilities to track application performance and scaling events.

88. Describe the process of deploying applications in OpenShift.

Ans:

 Applications in OpenShift are typically deployed using container images.

 Users define application configurations using YAML or JSON manifests.
 The deployment process involves creating pods, services, routes, and other resources as specified.
 OpenShift ensures application availability, scalability, and networking configuration during deployment.
 Rolling updates can be performed to deploy new versions without downtime.
 Continuous integration and delivery pipelines can automate the deployment process for efficiency.

89. How does OpenShift manage security for containerized applications?

Ans:
 OpenShift employs multiple layers of security mechanisms to protect containerized applications. It implements role-
based access controls (RBAC) to restrict access to resources based on user roles and permissions. Security contexts
and policies can be applied to individual containers to control their behavior and privileges. OpenShift scans container
images for vulnerabilities using built-in or third-party scanning tools.

90. What is the role of operators in OpenShift clusters?

Ans:

 Operators in OpenShift automate the management and lifecycle of complex applications.

 They encapsulate operational knowledge into software to handle tasks like deployment, scaling, and upgrades.
 Operators leverage Kubernetes Custom Resources and controllers to extend the platform’s functionality.
 Custom operators can be developed, or existing ones from the OperatorHub can be used.
 Operators ensure consistency, reliability, and efficiency in managing stateful and stateless applications.

Q1. What Is Openshift?

Answer : OpenShift is a cloud development Platform as a Service (PaaS) hosted by Red Hat. It’s an open

source technology which helps organizations move their traditional application infrastructure and platform

from physical, virtual mediums to the cloud. It supports a very large different of applications, which can be

easily developed and deployed on OpenShift cloud platform.

Q2. Why Use Open Shift?

Answer : OpenShift provides a common platform for enterprise units to host their applications on cloud

without worrying about the underlying operating system. This makes it very easy to use, develop, and

deploy applications on cloud. One of the key features is, it provides managed hardware and network

resources for all kinds of development and testing. With OpenShift, PaaS developer has the freedom to

design their required environment with specifications.

Q3. What Are The Features Of Openshift?

Answer : There are different features supported by Open Shift:

 Openshift has rich command line toolset.

 Multiple database and Language Support Provides support for continuous integration and release
management.
 Extensible Cartridge System
 One-Click Deployment
 Multi Environment Support
 Standardized Developers’ workflow
 Automatic Application Scaling
 Responsive Web Console
 Rich Command-line Toolset
 Provide support for remote SSH login to application.
 Rest API Support
 Self-service on Demand Application Stack
 Remote Debugging of Applications
 Built-in Database Services
 Continuous Integration and Release Management
 IDE Integration

Q4. What Is Openshift Origin?

Answer : OpenShift Origin is the upstream community project used in OpenShift Online, OpenShift

Dedicated, and OpenShift Container Platform. Built around a core of Docker container packaging and

Kubernetes container cluster management, Origin is augmented by application lifecycle management

functionality and DevOps tooling. Origin provides an open source application container platform. All

source code for the Origin project is available under the Apache License (Version 2.0) on GitHub.

Q5. What Is Openshift Online?

Answer : OpenShift Online is Red Hat’s public cloud application development and hosting service. It is an

offering of OpenShift community using which one can quickly build, deploy, and scale containerized

applications on the public cloud. It is Red Hat’s public cloud application development and hosting

platform, which enables automated provisioning, management and scaling of application which helps the

developer focus on writing application logic.

Q6. Explain Openshift Dedicated?

Answer : OpenShift Dedicated is Red Hat’s managed private cluster offering, built around a core of

application containers powered by Docker, with orchestration and management provided by Kubernetes,

on a foundation of Red Hat Enterprise Linux. It’s available on the Amazon Web Services (AWS) and

Google Cloud Platform (GCP) marketplaces.

Q7. What Is Openshift Enterprise?
Answer : OpenShift Enterprise by Red Hat is a Platform as a Service (PaaS) that provides developers

and IT organizations with an auto-scaling, cloud application platform for deploying new applications on

secure, scalable resources with minimal configuration and management overhead. OpenShift Enterprise

supports a wide selection of programming languages and frameworks, such as Java, Ruby, and PHP.

Integrated developer tools, such as Eclipse integration, JBoss Developer Studio, and Jenkins, support the

application life cycle.

Q8. What Is Routes In Openshift?

Answer : In OpenShift Routes is a way to externalize the services by providing externally reachable

hostname. In OpenShift routes are created using routers developed by admin.

Q9. What Is Source-to-image Strategy?

Answer : In this from source code images are created. In Source-to-image strategy source code is

downloaded and compiled and deployed in same container. From same code image is created.

Q10. What Is Openshift Container?

Answer : OpenShift Container Platform (formerly known as OpenShift Enterprise) is Red Hat’s on-

premises private platform as a service product, built around a core of application containers powered by

Docker, with orchestration and management provided by Kubernetes, on a foundation of Red Hat

Enterprise Linux.

Q11. What Is Automation?

Answer : OpenShift automates source code management, application builds, deployments, scaling, health

management and more.

Q12. What Is Pod?

Answer : A pod is collection of containers and its storage inside a node of a Kubernetes cluster. It is

possible to create a pod with multiple containers inside it. Following is an example of keeping a database

container and web interface container in the same pod.

Q13. What Are Stateful Pods?
Answer : StatefulSets are a Kubernetes feature that enables pods to be stopped and restarted while

retaining the same network address and storage attached to them. StatefulSets (PetSets in OCP 3.4) are

still an experimental feature, but full support should be added in an upcoming release.

Q14. What Are Deployment Strategies?

Answer : A deployment strategy is a way to change or upgrade an application. The aim is to make the

change without downtime in a way that the user barely notices the improvements. The most common

strategy is to use a blue-green deployment. The new version (the blue version) is brought up for testing

and evaluation, while the users still use the stable version (the green version). When ready, the users are

switched to the blue version. If a problem arises, you can switch back to the green version.

Q15. What Is Rolling Strategy?

Answer : A rolling deployment slowly replaces instances of the previous version of an application with

instances of the new version of the application. A rolling deployment typically waits for new pods to

become ready via a readiness check before scaling down the old components. If a significant issue

occurs, the rolling deployment can be aborted.

Q16. What Is Canary Deployments?

Answer : All rolling deployments in OpenShift Origin are canary deployments; a new version (the canary)

is tested before all of the old instances are replaced. If the readiness check never succeeds, the canary

instance is removed and the deployment.

Q17. What Is Deployment Pod Resources?

Answer : A deployment is completed by a pod that consumes resources (memory and CPU) on a node.

By default, pods consume unbounded node resources. However, if a project specifies default container

limits, then pods consume resources up to those limits. Another way to limit resource use is to (optionally)

specify resource limits as part of the deployment strategy.

Q18. What Is Blue/green Deployments?
Answer : The Blue/Green deployment strategy minimizes the time it takes to perform a deployment

cutover by ensuring you have two versions of your application stacks available during the deployment.

We can make use of the service and routing tiers to easily switch between our two running application

stacks—hence it is very simple and fast to perform a rollback.

Q19. Define Authentication In Openshift?

Answer : In OpenShift master has inbuilt OAuth server which generates tokens that can be used for API

authentication.

Q20. What Is Haproxy On Openshift?

Answer : On OpenShift, if your application is scalable, HAProxy sits in front of it and accepts all incoming

connections. It parses the HTTP protocol and decides which application instance the connection should

be routed to. This is important as it allows the user to have sticky sessions.

Q21. What is Haproxy?

Answer : If our application is scalable, then HAProxy will accept all the incoming connections. It analyzes

the HTTP protocol and determines to which instance of the application the connection is to be routed.

That’s important because it enables the user to get sticky sessions.

Q22. How gear differs from the container?

Answer : Both the words “gear” and “container” are interchangeable. The containers are accurately

mapped using one to one relations between the images. However, for gears, numerous cartridges may

form part of one gear. For containers, pods carry out the collocation concept.

Q23. What do you mean by Application Scaling?

Answer : In the OpenShift application, auto-scaling is also referred to as pod auto-scaling. Two kinds of

application scaling are available:

Vertical Scaling: To meet a higher load with vertical scaling, the application stays in the same place where

you provide it with more resources. For instance, you can add a bigger machine with faster CPUs, more

CPU, memory or disk space. The cost continues to increase with the addition of hardware resources.

Horizontal Scaling: To allow a higher load with the help of horizontal scaling, several instances of an

application are created, and application load is distributed among independent nodes.

With the expansion of the user base, the load and demand for applications increases. To maintain this

demand, we need either horizontal scaling or vertical scaling.

Q24. What is Openshift Online?

Answer : OpenShift online is the OpenShift community service that enables the rapid creation,

deployment and expansion of containerized applications in the public cloud. This is the platform for

development and hosting by Red Hat’s public cloud platform, that allows automated provisioning,

application scaling and management to assist developers in focusing on the development of the

framework logic.

Q25. What is Downward API?

Answer : The Downward API is a mechanism by which pods can fetch their metadata without the need for

the Kubernetes API. Following is the metadata that can be recovered and used for configuring the

running pods:

Annotations Labels Information related to Pod CPU/memory request and limit Namespace, Pod name,

and IP address Some information can be set up in the pod as an environment variable, while other

information is accessible as files in a volume.

Q26. Why Docker and Kubernetes in Openshift?

Answer: Docker assists in the creation of lightweight liner-based containers, whereas Kubernetes assists

in the orchestration and management of containers. OpenShift runs over Docker and Kubernetes. All the

containers are built over the Docker cluster, that is essentially the Kubernetes service over Linux

machines, with the help of the Kubernetes orchestration feature. In this process, we build a Kubernetes
 master that controls all nodes and will deploy containers across all nodes. Kubernetes’ primary purpose is

to control the OpenShift cluster and deployment flow with a different configuration file. Like in Kubernetes,

we use kubctl. Similarly, we use the OC command-line utility for developing and deploying containers on

the cluster nodes.

Q27. What is Volume Security?

Answer: Volume security signifies securing the PVC and PV of projects within the OpenShift cluster.

There are mostly four sections for controlling volume access within OpenShift.

 runAsUser
 fsGroup
 seLinuxOptions
 Supplemental Groups

Q28. Explain labels in Open-shift.

Answer: In OpenShift, the labels identify metadata that is made up of key/value pairs attached to the

resources. Labels can be used to add identifying attributes to the objects which are related to the users

and may be used to reflect the organizational or architectural concepts. Labels may be used in

combination with label selectors for identifying individual resources or the resource groups uniquely.

Examples: Tier, Relationship, Node types, etc.

Q29. What is the source-to-image strategy?

Answer: Source-to-image strategy is used to create source code images. This is achieved by

downloading and compiling the same container. The images are created according to the same code.

Within the customized strategy, jar and rpm are created.

Q30. Why choose Openshift?

Answer: OpenShift offers a common platform for business units to host their applications in the cloud

irrespective of the underlying operating system. This makes the use, development and deployment of

applications in the cloud extremely easy. A major feature is that it offers network resources and managed

hardware for all sorts of development and testing. With OpenShift, the PaaS developers are free to design

the environment they need with specifications.

Q31. Do you know about OpenShift cartridges?
Answer: OpenShift cartridges have also popped up as an important OpenShift interview question.

OpenShift cartridges are central points for developing applications. Every cartridge has specific libraries,

build mechanisms, source code, routing logic, and connection logic alongside pre-configured

environment. All these factors help in running your application.

Q32. What is the difference between gear and container?

Answer: You can find the latest OpenShift interview questions focused on difference-based evaluations.

The terms ‘container’ and ‘gear’ are interchangeable. Containers have a precise mapping involving one-

to-one relations among images. However, in the case of gears, many cartridges can become part of a

single gear. In the case of containers, pods fulfill the collocation concept.

Q33. What is the Source-to-Image (S2I) strategy?

Answer: This strategy involves the creation of source code images through downloading and compilation

of the same container. The images are created from the same code, and with a custom strategy, rpm and

jar get developed.

Q34. How OpenShift uses Docker and Kubernetes?

Answer: Kubernetes and Docker could work OpenShift in the form of a control system. You can find this

question among the latest OpenShift interview questions commonly. The control system helps in enabling

many deployment pipelines that are ideal for later use in auto-scaling, testing, and other processes.

Q35. What are the build strategies in OpenShift?

Answer: The common build strategies in OpenShift are Docker strategy, custom strategy, Source to

Image strategy, and pipeline strategy.

Q36. Why do we need DevOps tools?

Answer: The applications of DevOps tools are ideal for improving flexibility in software delivery. In addition

to this, DevOps tools also help in improving deployment frequency and reducing failure rates.

Furthermore, DevOps tools also help in faster recovery and better time management between repairs.
 Q37. What is the difference between OpenShift and
OpenStack?
Answer: Candidates can find this question among crucial OpenShift interview questions. The primary

difference is that OpenStack provides Infrastructure as a Service (IaaS). Furthermore, OpenStack is

different from OpenShift by providing object storage and block storage to a bootable virtual machine.

Q38. What are Build configurations?

Answer: Build configuration resources help in configuration and control of builds. Build configuration

includes details about a specific build strategy and the source of developer-supplied artifacts like output

image.

Q39. Name some identity providers in OAUTH.

Answer: The identity providers in OAUTH are HTTPassword, LDAP, Allow All, Deny All, and

Authentication.

Q40. Do you know about OpenShift Online?

Answer: OpenShift online is the public service of Red Hat for cloud application development and hosting.

Q41. Define routes and services in Openshift?

Answer: A pod is comprising services and containers; subsequently, service in Openshift is a get together

of coherent pods. The service is considered fundamentally as a REST object in Openshift. Routes are

given in Openshift to externalize and investigate the services needed to reach the hostname remotely. It

is achieved by utilizing the routes created by the admin commands.

Q42. Enlist a few build strategies that are used in

Openshift?
Answer: Following are the major build strategies used in Openshift:

 Custom Strategy
 Source to image Strategy
 Docker Strategy
 Pipeline Strategy
 Q43. Differentiate Openstack and Openshift?
Answer: The two of them are the original inception from open-source projects, and they similarly give

Cloud Computing essentials. The significant distinction between them is that OpenStack provides a

framework for administration or the structure ‘IaaS.’ It additionally provides object storage and blocks

storage to the bootable virtual machine. Then again, Openshift performs unexpectedly.

Q44. List out the most important features of Openshift?

Answer: Following are the prominent features of Openshift:

 It supports various databases and languages.

 Agreeable towards the environment sustain.
 It seriously gives a web console.
 It gives remote debugging.
 It has the capability of a rich command-line tool.
 It helps to remote login to the application through SSH.

Q45. Explain about Openshift Deployment?

Answer: Deployment in OpenShift is a replication regulator dependent on a user-defined layout called a

deployment arrangement. Deployments are composed or in response to triggered functions. The

deployment framework gives the accompanying:

 A deployment arrangement is a layout for deployments.

 Triggers that drive computerized organizations in response to occasions.
 Client adaptable strategies to progress from the previous arrangement to the new deployments. Rollbacks
to preceding deployments.
 Manual replication scaling.

Q46. Explain the deployment strategies?

Answer: An organization technique is an approach to change an application or to refresh it. The objective

is to make progress such that the buyer scarcely sees the changes, without personal time. Utilizing a

blue-green sending is the most standard method.

The new form (the blue variant) is being worked for testing and assessment, while the clients utilize the

steady-state (the green). The clients are moved to the blue adaptation when it’s accessible. You can

return to the Green form if an issue happens.

 Q47. Explain the rolling strategy?
Answer: A moving rollout slowly replaces examples of an application’s earlier form with cases of the

application’s present rendition. A rolling deployment typically trusts that new units will prepare through a

status test until the old modules are downsized. The moving organization can be stopped if a problematic

issue happens.

Q48. Explain about the Canary Deployments?

Answer: All rolling organizations in OpenShift Origin are canary arrangements; it checks another

adaptation (the canary) before supplanting all the old examples. Except if the availability test never works,

at that point, the canary occasion and sending will be handicapped.

Q49. Explain about Openshift Online?

Answer: OpenShift Online is an OpenShift people group administration that permits one to make, convey,

and scale containerized applications on the public cloud rapidly. It is the turn of events and facilitates the

foundation of Red Hat’s public cloud stage, which empowers automated provisioning, the board, and

application scaling to help designers focus on the advancement of system rationale.

Q50. Explain about DevOps?

Answer: DevOps assist associations with reacting a more agile way of changing business prerequisites

by:

 Computerizing and observing the cycle of programming creation,

 from a mix, testing, delivering to sending, and overseeing it.
 Smoothing out the turn of events and delivery pipeline
 Expanding the deployment recurrence.
 Decreasing the advancement cycles.