Skip to content

Milestones

List view

  • v1.33

    Due by April 25, 2025
    •374/374 issues closed
    100% complete0 open374 closed

  • v1.32

    Due by November 30, 2024
    •408/408 issues closed
    100% complete0 open408 closed

  • v1.31

    Due by August 30, 2024
    •407/407 issues closed
    100% complete0 open407 closed

  • v1.30

    Due by March 29, 2024
    •496/496 issues closed
    100% complete0 open496 closed

  • v1.29

    No due date
    •409/409 issues closed
    100% complete0 open409 closed

  • v1.28

    No due date
    •610/610 issues closed
    100% complete0 open610 closed

  • v1.27

    Tracking milestone for v1.27

    No due date
    •410/412 issues closed
    99% complete2 open410 closed

  • v1.26

    Due by December 15, 2022
    •3/3 issues closed
    100% complete0 open3 closed

  • v1.25

    Due by August 23, 2022
    •587/587 issues closed
    100% complete0 open587 closed

  • v1.24

    Due by April 1, 2022
    •472/472 issues closed
    100% complete0 open472 closed

  • v1.23

    Due by December 7, 2021
    •647/647 issues closed
    100% complete0 open647 closed

  • v1.22

    Due by August 4, 2021
    •517/517 issues closed
    100% complete0 open517 closed

  • v1.21

    Due by March 31, 2021
    •294/294 issues closed
    100% complete0 open294 closed

  • migrate-k8s-tests

    Migrate everything related to the use of prow.k8s.io to run tests for the project, store results, report status back to github, etc. Talking specifically of k8s-tests here because earlier milestones may involve setting up a basic prow cluster to run trusted jobs here

    Due by September 30, 2019
    0% complete0 open0 closed

  • migrate-low-risk

    Migrate over low-risk, non-entangled infra(this likely means anything that is not part of prow.k8s.io directly) Swag: - focus on cluster-based infra - k8s.gcr.io image promotion process for all container images

    Due by August 31, 2019
    •4/4 issues closed
    100% complete0 open4 closed

  • proof-of-concept

    Retroactive milestone to document what we have done as part of wg-k8s-infra thus far. Closure of all issues in this milestone means we're ready to automate our work and move forward Swag: - we have a gcp account and a dedicated wg - we can generate and review billing reports at each wg-k8s-infra (in aggregate, for the account) - we have a temporary cluster setup for cluster-based infra, and two services migrated to it - we have a non-cluster-based service migrated (DNS) - we have a proposal to host project artifacts (GCS, GCR)

    Due by April 30, 2019
    •6/6 issues closed
    100% complete0 open6 closed

  • ready-to-migrate

    What is preventing us from migrating all existing project infrastructure over? Closure of all issues in this milestone means we are ready to begin migrating project infrastructure Swag: - we have an agreed upon prioritized backlog of infra to migrate - we can generate and review billing reports at each wg-k8s-infra meeting (in detail) - we can inventory what groups/roles we have and who is in them - we can rebuild/redeploy cluster-based infra, and have done so at least twice - we can use a k8s.gcr.io image promotion process for core kubernetes component images

    Due by July 31, 2019
    •19/19 issues closed
    100% complete0 open19 closed