Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

feat: mount propagation documentation in feature flags #6223

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.

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

Open
elijah-rou wants to merge 2 commits into knative:main
base: main
Choose a base branch
Loading
from elijah-rou:feat/mount-prop-docs

Conversation

Copy link

@elijah-rou elijah-rou commented Feb 12, 2025

Adds mountPropagation to the features/extensions page. For knative/serving#15758

Copy link

knative-prow bot commented Feb 12, 2025

Welcome @elijah-rou! It looks like this is your first PR to knative/docs 🎉

@knative-prow knative-prow bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Feb 12, 2025
Copy link

netlify bot commented Feb 12, 2025
edited
Loading

Deploy Preview for knative ready!

Name Link
🔨 Latest commit 91de3d6
🔍 Latest deploy log https://app.netlify.com/projects/knative/deploys/68a5e3bd5a11030008f01233
😎 Deploy Preview https://deploy-preview-6223--knative.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link
Member

@dprotaso dprotaso left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we undo the formatting that's not related to the feature flag you're adding?


!!! note
Extensions are never included in the core Knative API due to their lack of portability.
Extensions are never included in the core Knative API due to their lack of portability.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the prior indent is intentional - otherwise the note block doesn't render properly

apiVersion: serving.knative.dev/v1
kind: Service
...
---
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

don't want this change - we're just using ... to elide the metadata

apiVersion: serving.knative.dev/v1
kind: Service
...
---
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

likewise above

Copy link
Member

hey @elijah-rou just following up on this

Copy link

This Pull Request is stale because it has been open for 90 days with
no activity. It will automatically close after 30 more days of
inactivity. Reopen with /reopen. Mark as fresh by adding the
comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 17, 2025
Copy link

knative-prow bot commented Aug 20, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: elijah-rou
Once this PR has been reviewed and has the lgtm label, please ask for approval from dprotaso. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Copy link
Member

@elijah-rou any chance you could address these docs changes?

@github-actions github-actions bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 21, 2025
Copy link
Member

dprotaso commented Sep 8, 2025

@elijah-rou just following up here

@knative-prow-robot knative-prow-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 20, 2025
Copy link
Contributor

PR needs rebase.

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.

Copy link
Member

Sorry about the merge -- in #6398 , I moved all the versioned documentation under versioned, to separate it from the blog, testimonials, community pages that are not version-specific. You should be able to just move these files to the new location; I didn't need to change any contents.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@dprotaso dprotaso dprotaso requested changes

@csantanapr csantanapr Awaiting requested review from csantanapr

@zainabhusain227 zainabhusain227 Awaiting requested review from zainabhusain227

Labels

needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

AltStyle によって変換されたページ (->オリジナル) /