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

Figure out documentation layout #2

Closed
bprashanth opened this issue Nov 10, 2016 · 2 comments
Closed

Figure out documentation layout #2

bprashanth opened this issue Nov 10, 2016 · 2 comments
Labels
area/docs

Comments

@bprashanth
Copy link
Contributor

We have a chance to improve the way we handle docs/examples since we're moving to a new repo, lets not waste it. Ideas on how we should lay out examples ?
@aledbf @mdelio @justinsb

One idea mentioned was to use https://github.com/apiaryio/api-blueprint/tree/master/examples to handle documentation and testing for cross platform cases kubernetes-retired/contrib#775
@bprashanth bprashanth added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Nov 10, 2016
@bprashanth bprashanth mentioned this issue Nov 10, 2016
Closed
@bprashanth bprashanth removed the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Nov 10, 2016
@aledbf
Copy link
Member

aledbf commented Nov 10, 2016

Using https://apiblueprint.org/ is possible to express one or more test cases just using markdown files. Is possible to extend the recognized tags so is possible to add particular things like all the related to kubernetes. Something like this:
captura de pantalla 2016-11-08 a las 10 22 18 a m

with this approach is easy to add new tests (e2e), any user can build a new test case and use this format as a standard way to express the intent using standard kubernetes api objects and also enable the use of custom docker user images.

@bprashanth
Copy link
Contributor Author

Can you stand up a POC in your repo?

@bprashanth bprashanth mentioned this issue Nov 28, 2016
Merged
@yissachar yissachar mentioned this issue Feb 10, 2017
Closed
@aledbf aledbf closed this as completed Oct 3, 2017
@tagarwal tagarwal mentioned this issue Oct 12, 2017
Closed
@riker09 riker09 mentioned this issue Jan 24, 2020
Closed
@marianobilli marianobilli mentioned this issue Dec 16, 2020
Closed
haoqing0110 referenced this issue in stolostron/management-ingress Mar 5, 2021
@qiujian16
Deploy example (#2)
342fcde 
* Update Readme

* Add deploy manifest

* Add examples and deploy manifest
haoqing0110 referenced this issue in stolostron/management-ingress Mar 5, 2021
@ckandag
Merge pull request #2 from open-cluster-management/oauthproxy-updates
f07c686 
outh proxy updates
@daninthewoods daninthewoods mentioned this issue Apr 9, 2021
Closed
@derek-burdick derek-burdick mentioned this issue Sep 25, 2021
Closed
@jamesmmccarthy jamesmmccarthy mentioned this issue Nov 23, 2021
Closed
@mareq mareq mentioned this issue Dec 2, 2021
Closed
XiShanYongYe-Chang pushed a commit to XiShanYongYe-Chang/ingress-nginx that referenced this issue Feb 25, 2022
@karmada-bot
Merge pull request kubernetes#2 from XiShanYongYe-Chang/donot-run-e2e
ae6f8c4 
do not run e2e first
@sskserk sskserk mentioned this issue Mar 11, 2022
Merged
9 tasks
YngveMolnes pushed a commit to YngveMolnes/ingress-nginx that referenced this issue May 25, 2023
# This is a combination of 5 commits.
3eed9f3 
# This is the 1st commit message:

Add feature flag to disable annotation prefix check in admission controller

# This is the commit message kubernetes#2:

Add log message for when ingress hits annotation check

Indicates that the correct environment variable is set. Does not log on
absence of environment variable.

# This is the commit message kubernetes#3:

Add flag for disabling legacy ingress class annotation prefix check

# This is the commit message kubernetes#4:

Remove negation from if statement on annotation prefix check

# This is the commit message kubernetes#5:

Add logline to indicate annotation prefix check is skipped
@alphabet5 alphabet5 mentioned this issue May 2, 2024
Open
@bagaderohit bagaderohit mentioned this issue Sep 6, 2024
Closed
@stex79 stex79 mentioned this issue Oct 25, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/docs
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@aledbf @bprashanth