github/awesome-kubernetes
1
0
Fork 0
mirror of https://github.com/nubenetes/awesome-kubernetes.git synced 2026-03-05 03:00:37 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
dd7ceca4e01bc448ea2bef9c986cb767637f89c5
awesome-kubernetes/docs/openshift.md
Inaki Fernandez db8ddceb69 stars cleanup
2020-05-12 15:59:24 +02:00

40 KiB
Raw Blame History

OpenShift Container Platform

OpenShift

Red Hat's approach to Kubernetes. Standardization

Reference Author URL
"Given the difficulty of navigating the cloud-native ecosystem, especially the one around Kubernetes, there is a high demand for easy-to-administer development platforms that deliver applications in Kubernetes-managed containers." OMDIA Red Hat's approach to Kubernetes
Industry momentum has aligned behind Kubernetes as the orchestration platform for Linux® containers. Choosing Kubernetes means you’ll be running the de facto standard regardless of which cloud environments and providers are in your future. CNCF Survey 2019 Red Hat's approach to Kubernetes
“It's not just enough to do Kubernetes. You do need to do CI/CD. You need to use alerting. You need to understand how the security model of the cloud and your applications interplay.” Clayton Coleman,Senior Distinguished Engineer, Red Hat Red Hat's approach to Kubernetes
“Kubernetes is scalable. It helps develop applications faster. It does hybrid and multicloud. These are not just technology buzzwords, they're real, legitimate business problems.” Brian Gracely,Director, Product Strategy, Red Hat OpenShift Red Hat's approach to Kubernetes
“Our job is to make it easier and easier to use, either from an ops point of view or a developer point of view—while acknowledging it is complex, because we're solving a complex problem.” Chris Wright,Chief Technology Officer, Red Hat Red Hat's approach to Kubernetes

OpenShift Container Platform 3 (OCP 3)

OpenShift Cheat Sheets

Helm Charts and OpenShift 3

Chaos Monkey for kubernetes/Openshift

OpenShift GitOps

Debugging apps

Capacity Management

OpenShift High Availability

Troubleshooting Java applications on Openshift

Red Hat Communities of Practice. Uncontained.io Project

Identity Management

Quota Management

OpenShift Container Platform 4 (OCP 4)

OCP 4 Architecture

OpenShift Youtube

OpenShift 4 Training

OpenShift 4 roadmap

Kubevirt Virtual Machine Management on Kubernetes

Storage in OCP 4. OpenShift Container Storage (OCS)

Red Hat Advanced Cluster Management for Kubernetes

OpenShift Kubernetes Engine (OKE)

openshift4 architecture

Red Hat CodeReady Containers. OpenShift 4 on your laptop

OpenShift Hive: Cluster-as-a-Service. Easily provision new PaaS environments for developers

OpenShift 4 Master API Protection in Public Cloud

Backup and Migrate to OpenShift 4

OKD4. OpenShift 4 without enterprise-level support

OpenShift Serverless with Knative

Helm Charts and OpenShift 4

Red Hat Marketplace

Kubestone. Benchmarking Operator for K8s and OpenShift

OpenShift Cost Management

Operators in OCP 4

Quay Container Registry

OpenShift.io online IDE

  • openshift.io 🌟 an online IDE for building container-based apps, built for team collaboration.

Cluster Autoscaler in OpenShift

e-Books

Kubernetes e-Books

Online Learning

Local Installers

Cluster Installers

OKD 3

OpenShift 3

OpenShift 4

OpenShift 4 deployment on vSphere

Networking (OCP 3 and OCP 4)

Security

How is OpenShift Container Platform Secured?

Security Context Constraints

Review Security Context Constraints

  • Security Context Constraints (SCCs) control what actions pods can perform and what resources they can access.
  • SCCs combine a set of security configurations into a single policy object that can be applied to pods. These security configurations include, but are not limited to, Linux Capabilities, Seccomp Profiles, User and Group ID Ranges, and types of mounts.
  • OpenShift ships with several SCCs. The most constrained is the restricted SCC, and the least constrained in the privileged SCC. The other SCCs provide intermediate levels of constraint for various use cases. The restricted SCC is granted to all authenticated users by default.
  • The default SCC for most pods should be the restricted SCC. If required, a cluster administrator may allow certain pods to run with different SCCs. Pods should be run with the most restrictive SCC possible.
  • Pods inherit their SCC from the Service Account used to run the pod. With the default project template, new projects get a Service Account named default that is used to run pods. This default service account is only granted the ability to run the restricted SCC.
  • Recommendations:
    • Use OpenShift's Security Context Constraint feature, which has been contributed to Kubernetes as Pod Security Policies. PSPs are still beta in Kubernetes 1.10, 1.11, and 1.12.
    • Use the restricted SCC as the default
    • For pods that require additional access, use the SCC that grants the least amount of additional privileges or create a custom SCC Audit
    • To show all available SCCs: oc describe scc
    • To audit a single pod: oc describe pod <POD> | grep openshift.io\/scc
    • Remediation: Apply the SCC with the least privilege required

Network Policy

Network Security Zones

Openshift Compliant Docker Images

Gitlab

Atlassian Confluence6

Sonatype Nexus 3

Rocket Chat

OpenShift on AWS

Other Awesome Lists

Videos

Slides

Reference in New Issue View Git Blame Copy Permalink