website
website copied to clipboard
kubernetes
Update training to mention PCA
This is a Feature Request
What would you like to be added As suggested in https://github.com/cncf/techdocs/issues/139:
- update the training page (https://kubernetes.io/training/) to include a reference to PCA (in the Get Kubernetes Certified section): https://www.cncf.io/certification/pca/
- Update section name from "Get Kubernetes Certified" to "Get Kubernetes and Cloud Native Certifications"
Why is this needed
To increase awareness of related cloud native certifications
@nate-double-u: This issue is currently awaiting triage.
SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.
The triage/accepted label can be added by org members by writing /triage accepted in a comment.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
@thisisobate: GitHub didn't allow me to assign the following users: me.
Note that only kubernetes members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see the contributor guide
In response to this:
Would love to take on this issue. /assign me
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
The content guide doesn't make it clear that this is or isn't OK, as the training page is outside of our docs.
It's a switch from the spirit of the content guide, though: previously, we explicitly didn't favor projects that were part of the LF / CNCF over other vendors' projects. If we're now doing that, I suggest we go through an enhancement proposal to make the new policy clear.
Maybe we change the top nav to take people to https://www.cncf.io/certification/training/#kubernetes and annotate the “Training” item with an icon to hint that it's an off-site link?
To make that work, we / CNCF could put some time into making https://www.cncf.io/certification/training/#kubernetes be a working fragment.
Maybe we change the top nav to take people to https://www.cncf.io/certification/training/#kubernetes and annotate the “Training” item with an icon to hint that it's an off-site link?
Sounds like a good idea. Your thoughts? @nate-double-u @caniszczyk
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle stale - Mark this issue or PR as rotten with
/lifecycle rotten - Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
Maybe we change the top nav to take people to https://www.cncf.io/certification/training/#kubernetes and annotate the “Training” item with an icon to hint that it's an off-site link?
To make that work, we / CNCF could put some time into making https://www.cncf.io/certification/training/#kubernetes be a working fragment.
Do you mean completely removing the https://kubernetes.io/training/ page, and linking the top nav to the cncf.io training site? (We'd have to update the cncf training page to include the #kubernetes anchor). I expect we'd need to work with the sig-docs chairs to approve, but I think this is an interesting idea. It also means that there is one less K8s website page to maintain.
…completely removing the https://kubernetes.io/training/ page, and linking the top nav to the cncf.io training site?
Yes, that or something very similar. Requires that we can make https://www.cncf.io/certification/training/#kubernetes (or https://www.cncf.io/certification/training/kubernetes) be a real thing.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
Maybe we change the top nav to take people to https://www.cncf.io/certification/training/#kubernetes and annotate the “Training” item with an icon to hint that it's an off-site link?
To make that work, we / CNCF could put some time into making https://www.cncf.io/certification/training/#kubernetes be a working fragment.
+1 to this. Thoughts @natalisucks @reylejano ?
Wouldn't recommend making this a web development issue just yet and we should consider waiting till all parties are in agreement, @aj11anuj. Once we've agreed upon the approach, we can classify it appropriately.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle rotten - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Reopen this issue with
/reopen - Mark this issue as fresh with
/remove-lifecycle rotten - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
In response to this:
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied- After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied- After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closedYou can:
- Reopen this issue with
/reopen- Mark this issue as fresh with
/remove-lifecycle rotten- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.