Skip to content

OCPBUGS-31666: Bump openshift/api for Route API godoc fix#433

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:masterfrom
Miciah:OCPBUGS-31666-bump-openshift-slash-api-for-Route-API-godoc-fix
May 8, 2024
Merged

OCPBUGS-31666: Bump openshift/api for Route API godoc fix#433
openshift-merge-bot[bot] merged 1 commit intoopenshift:masterfrom
Miciah:OCPBUGS-31666-bump-openshift-slash-api-for-Route-API-godoc-fix

Conversation

@Miciah
Copy link
Contributor

@Miciah Miciah commented Apr 30, 2024

Bump to openshift/api@8203151, which fixes the godoc for the Route.spec.tls.insecureEdgeTerminationPolicy field to say that "None", not "Allow", is the default value.

Bump to openshift/library-go@cb8aac9 to fix build errors in library-go resulting from changes in openshift/api.

Update NewOpenshiftAPIConfig likewise to read feature definitions from their new location in openshift/api.

Follow-up to openshift/api#1845.

@openshift-ci-robot openshift-ci-robot added jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Apr 30, 2024
@openshift-ci-robot
Copy link

@Miciah: This pull request references Jira Issue OCPBUGS-31666, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.16.0) matches configured target version for branch (4.16.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @ShudiLi

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Bump to github.com/openshift/api@8203151f085f2205ba7fa64f093a04a742d1cb87, which fixes the godoc for the Route.spec.tls.insecureEdgeTerminationPolicy field to say that "None", not "Allow", is the default value.

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 openshift-eng/jira-lifecycle-plugin repository.

@Miciah Miciah force-pushed the OCPBUGS-31666-bump-openshift-slash-api-for-Route-API-godoc-fix branch from 4b0a7a5 to f15a6b9 Compare May 1, 2024 13:14
@Miciah
Copy link
Contributor Author

Miciah commented May 1, 2024

https://github.com/openshift/openshift-apiserver/compare/4b0a7a5ef1bcdcb7dfc6fed1f89b0632ecd11d96..f15a6b96f2cf13e83ac665f3c644e51b36be2744 bumps the vendored library-go to fix build errors that resulted from the openshift/api bump.

@Miciah Miciah force-pushed the OCPBUGS-31666-bump-openshift-slash-api-for-Route-API-godoc-fix branch from f15a6b9 to b3335a8 Compare May 1, 2024 14:54
@Miciah
Copy link
Contributor Author

Miciah commented May 1, 2024

@openshift-ci-robot
Copy link

@Miciah: This pull request references Jira Issue OCPBUGS-31666, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.16.0) matches configured target version for branch (4.16.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @ShudiLi

Details

In response to this:

Bump to github.com/openshift/api@8203151f085f2205ba7fa64f093a04a742d1cb87, which fixes the godoc for the Route.spec.tls.insecureEdgeTerminationPolicy field to say that "None", not "Allow", is the default value.

Bump to github.com/openshift/library-go@cb8aac942b79e973d2c37168ccff36c882200856 to fix build errors in library-go resulting from changes in openshift/api.

Update NewOpenshiftAPIConfig likewise to read feature definitions from their new location in openshift/api.

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 openshift-eng/jira-lifecycle-plugin repository.

Bump to github.com/openshift/api@8203151f085f2205ba7fa64f093a04a742d1cb87,
which fixes the godoc for the Route.spec.tls.insecureEdgeTerminationPolicy
field to say that "None", not "Allow", is the default value.  Bump to
github.com/openshift/library-go@cb8aac942b79e973d2c37168ccff36c882200856
to fix build errors in library-go resulting from changes in openshift/api.
Update NewOpenshiftAPIConfig likewise to read feature definitions from
their new location in openshift/api.

    go get github.com/openshift/api@8203151f085f2205ba7fa64f093a04a742d1cb87 \
     github.com/openshift/library-go@cb8aac942b79e973d2c37168ccff36c882200856
    go mod tidy
    go mod vendor

This commit fixes OCPBUGS-31666.

https://issues.redhat.com/browse/OCPBUGS-31666

* go.mod: Bump.
* go.sum:
* hack/openapi-violation.list:
* pkg/openapi/zz_generated.openapi.go:
* vendor/*: Regenerate.
* pkg/cmd/openshift-apiserver/cmd.go (RunAPIServer):
* pkg/cmd/openshift-apiserver/openshiftapiserver/config.go
(NewOpenshiftAPIConfig): Read feature definitions from their new location
in the "github.com/openshift/api/features" package.
@Miciah Miciah force-pushed the OCPBUGS-31666-bump-openshift-slash-api-for-Route-API-godoc-fix branch from b3335a8 to b983b70 Compare May 2, 2024 03:34
@Miciah
Copy link
Contributor Author

Miciah commented May 2, 2024

@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 2, 2024

@Miciah: all tests passed!

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.

@ShudiLi
Copy link
Member

ShudiLi commented May 8, 2024

tested it with 4.16.0-0.ci.test-2024-05-08-031552-ci-ln-hmrbdf2-latest: If a route does not specify insecureEdgeTerminationPolicy, then the default behavior is "None".

1.
% oc get clusterversion   
NAME      VERSION                                                   AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.16.0-0.ci.test-2024-05-08-031552-ci-ln-hmrbdf2-latest   True        False         6m17s   Cluster version is 4.16.0-0.ci.test-2024-05-08-031552-ci-ln-hmrbdf2-latest
% 

2.
% oc explain routes.spec.tls.insecureEdgeTerminationPolicy
GROUP:      route.openshift.io
KIND:       Route
VERSION:    v1

FIELD: insecureEdgeTerminationPolicy <string>

DESCRIPTION:
    insecureEdgeTerminationPolicy indicates the desired behavior for insecure
    connections to a route. While each router may make its own decisions on
    which ports to expose, this is normally port 80.
    
    If a route does not specify insecureEdgeTerminationPolicy, then the default
    behavior is "None".
    
    * Allow - traffic is sent to the server on the insecure port (edge/reencrypt
    terminations only).
    
    * None - no traffic is allowed on the insecure port (default).
    
    * Redirect - clients are redirected to the secure port.
    

%

@ShudiLi
Copy link
Member

ShudiLi commented May 8, 2024

/label qe-approved
thanks

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label May 8, 2024
@p0lyn0mial
Copy link
Contributor

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 8, 2024
@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 8, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Miciah, p0lyn0mial

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

The pull request process is described here

Details 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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 8, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit 11d295e into openshift:master May 8, 2024
@openshift-ci-robot
Copy link

@Miciah: Jira Issue OCPBUGS-31666: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-31666 has been moved to the MODIFIED state.

Details

In response to this:

Bump to openshift/api@8203151, which fixes the godoc for the Route.spec.tls.insecureEdgeTerminationPolicy field to say that "None", not "Allow", is the default value.

Bump to openshift/library-go@cb8aac9 to fix build errors in library-go resulting from changes in openshift/api.

Update NewOpenshiftAPIConfig likewise to read feature definitions from their new location in openshift/api.

Follow-up to openshift/api#1845.

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-openshift-apiserver-container-v4.17.0-202405080245.p0.g11d295e.assembly.stream.el9 for distgit ose-openshift-apiserver.
All builds following this will include this PR.

@openshift-merge-robot
Copy link
Contributor

Fix included in accepted release 4.16.0-0.nightly-2024-05-08-222442

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

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. qe-approved Signifies that QE has signed off on this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants