Skip to content

Bump to k8s.io/ v0.27.2 #2297

Description

@sbueringer

Goal of this issue is to bump to v0.27.2

While bumping to v0.27.1 we had to disable unit tests that verified the correct log format of a namespaced name (#2189, test: https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_controller-runtime/2189/pull-controller-runtime-test/1651556343619784704).

As part of bumping to v0.27.2 we will enable those tests again

Note: We will wait with the v0.15.0 release until we bumped to v0.27.2.

Links:

Activity

  1. added this to the v0.15.x milestone on May 3, 2023
  2. added
    kind/regressionCategorizes issue or PR as related to a regression from a prior release.
    on May 3, 2023
  3. liggitt commented on May 4, 2023

    @liggitt

    While bumping to v0.27.1 we had to disable unit tests that verified the correct log format of a namespaced name

    log output is not a guaranteed API (xref kubernetes/kubernetes#117238 (comment))... I'd strongly suggest removing a hard dependency on a particular format and bumping the version now

  4. liggitt commented on May 4, 2023

    @liggitt

    oh... I guess #2189 already bumped and this is waiting to bump again to tag a release?

  5. mythi commented on May 4, 2023

    @mythi
    Contributor

    @liggitt yes. the tests failing on a specific log format are now skipped. this is just to track 0.27.2 to do another bump

  6. sbueringer commented on May 4, 2023

    @sbueringer
    MemberAuthor

    Yup. This issue is just to wait for v0.27.2 in 2 weeks. For now we also enable our unit tests again that - as of now - ensure the log format doesn't change.

    I think it should be a separate discussion if we want to drop the unit tests. As far as I'm aware we also don't strictly guarantee that our log output is stable, but we try to only break it when necessary to provide users some stability if possible.

    (But we are absolutely aware that there are no guarantees from k/k)

  7. sbueringer commented on May 4, 2023

    @sbueringer
    MemberAuthor

    In this case the trade-off for us was basically release CR v0.15.0 with a changed log format and v0.15.1 would change it back or do we delay the release until mid May.

  8. kkkkun commented on May 18, 2023

    @kkkkun
    Member

    In this case the trade-off for us was basically release CR v0.15.0 with a changed log format and v0.15.1 would change it back or do we delay the release until mid May.

    kubernetes:v1.27.2 is released https://github.com/kubernetes/kubernetes/releases/tag/v1.27.2

  9. sbueringer commented on May 18, 2023

    @sbueringer
    MemberAuthor

    /reopen
    log tests weren't enabled again yet

  10. k8s-ci-robot commented on May 18, 2023

    @k8s-ci-robot
    Contributor

    @sbueringer: Reopened this issue.

    Details

    In response to this:

    /reopen
    log tests weren't enabled again yet

    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.

  11. blkperl commented on May 18, 2023

    @blkperl

    Can someone please tag a new release now that this is fixed?

  12. dongjiang1989 commented on May 19, 2023

    @dongjiang1989
    Member

    Please release a new version? #2320

  13. vincepri commented on May 19, 2023

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/regressionCategorizes issue or PR as related to a regression from a prior release.

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions