Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

typos #23

Closed
wants to merge 1 commit into from
Closed

typos #23

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/unit09/k8s_intro.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -128,7 +128,7 @@ namespace where their k8s objects would live, and users wouldn't have access to

That is how the class Kubernetes cluster has been set up. Each of you has been assigned your own namespace
in the Kubernetes cluster where you have administrative access. Inside that namespace, you can create
and manage the Kubernetes objects for your application. And while all of the Kubernetes objects for every
and manage the Kubernetes objects of your application. And while all of the Kubernetes objects for every
student is running on the same cluster, you won't see or have access to the objects in different namespaces.

We haven't introduced `pods` yet -- we will shortly -- but let's try a simple experiment: issue
Expand Down