microshift

microshift copied to clipboard

In response to this:

TODO:

• [ ] Generate Lister / Typed Clients due to otherwise mandatory import on lvm-operator introducing tons of dependencies
• [ ] Resolve vendor conflict (see above) with normal resolution instead of vendor patch
• [ ] Create Cleanup Scenario that deletes old set of resources from installations that were present in 4.15/4.16
• [ ] Add upgrade test scenario to verify that LVMS works as expected
• [ ] Add webhook yaml generation as part of the rebase script so that the validatingwebhook configuration is applied to LVMCluster normally

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.

In response to this:

TODO:

• [ ] Generate Lister / Typed Clients due to otherwise mandatory import on lvm-operator introducing tons of dependencies
• [ ] Resolve vendor conflict (see above) with normal resolution instead of vendor patch
• [ ] Create Cleanup Scenario that deletes old set of resources from installations that were present in 4.15/4.16
• [ ] Add upgrade test scenario to verify that LVMS works as expected
• [ ] Add webhook yaml generation as part of the rebase script so that the validatingwebhook configuration is applied to LVMCluster normally
• [ ] Use 4.17 Candidate instead of late 4.16 candidate once we have a CPaaS build out in the wild (need to trigger external replication that can be used during 4.17 testing cycle)

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.

In response to this:

TODO:

• [ ] Generate Lister / Typed Clients due to otherwise mandatory import on lvm-operator introducing tons of dependencies
• [ ] Resolve vendor conflict (see above) with normal resolution instead of vendor patch
• [ ] Create Cleanup Scenario that deletes old set of resources from installations that were present in 4.15/4.16
• [ ] Add upgrade test scenario to verify that LVMS works as expected
• [ ] Add webhook yaml generation as part of the rebase script so that the validatingwebhook configuration is applied to LVMCluster normally
• [ ] Use 4.17 Candidate instead of late 4.16 candidate once we have a CPaaS build out in the wild (need to trigger external replication that can be used during 4.17 testing cycle)
• [ ] Rebase on main

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.

In response to this:

TODO:

• [X] ~Generate Lister / Typed Clients due to otherwise mandatory import on lvm-operator introducing tons of dependencies~ replaced with a generic unstructured client
• [X] Resolve vendor conflict (see above) with normal resolution instead of vendor patch
• [ ] Create Cleanup Scenario that deletes old set of resources from installations that were present in 4.15/4.16
• [ ] Add upgrade test scenario to verify that LVMS works as expected
• [ ] Add webhook yaml generation as part of the rebase script so that the validatingwebhook configuration is applied to LVMCluster normally
• [ ] Use 4.17 Candidate instead of late 4.16 candidate once we have a CPaaS build out in the wild (need to trigger external replication that can be used during 4.17 testing cycle)
• [ ] Rebase on main

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.

In response to this:

TODO:

• [X] ~Generate Lister / Typed Clients due to otherwise mandatory import on lvm-operator introducing tons of dependencies~ replaced with a generic unstructured client
• [X] Resolve vendor conflict (see above) with normal resolution instead of vendor patch
• [ ] Create Cleanup Scenario that deletes old set of resources from installations that were present in 4.15/4.16
• [ ] Add upgrade test scenario to verify that LVMS works as expected
• [x] Add webhook yaml generation as part of the rebase script so that the validatingwebhook configuration is applied to LVMCluster normally
• [ ] Use 4.17 Candidate instead of late 4.16 candidate once we have a CPaaS build out in the wild (need to trigger external replication that can be used during 4.17 testing cycle)
• [ ] Rebase on main

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.

In response to this:

TODO:

• [X] ~Generate Lister / Typed Clients due to otherwise mandatory import on lvm-operator introducing tons of dependencies~ replaced with a generic unstructured client
• [X] Resolve vendor conflict (see above) with normal resolution instead of vendor patch
• [ ] Create Cleanup Scenario that deletes old set of resources from installations that were present in 4.15/4.16
• [ ] Add upgrade test scenario to verify that LVMS works as expected
• [x] Add webhook yaml generation as part of the rebase script so that the validatingwebhook configuration is applied to LVMCluster normally
• [ ] Use 4.17 Candidate instead of late 4.16 candidate once we have a CPaaS build out in the wild (need to trigger external replication that can be used during 4.17 testing cycle)
• [ ] Add dynamic lvmd.yaml resolution via symlink into /var/lib/microshift/lvms/lvmd.yaml
• [ ] Rebase on main

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.

In response to this:

TODO:

• [X] ~Generate Lister / Typed Clients due to otherwise mandatory import on lvm-operator introducing tons of dependencies~ replaced with a generic unstructured client
• [X] Resolve vendor conflict (see above) with normal resolution instead of vendor patch
• [ ] Create Cleanup Scenario that deletes old set of resources from installations that were present in 4.15/4.16
• [ ] Add upgrade test scenario to verify that LVMS works as expected
• [x] Add webhook yaml generation as part of the rebase script so that the validatingwebhook configuration is applied to LVMCluster normally
• [ ] Use 4.17 Candidate instead of late 4.16 candidate once we have a CPaaS build out in the wild (need to trigger external replication that can be used during 4.17 testing cycle)
• [x] Add dynamic lvmd.yaml resolution via symlink into /var/lib/microshift/lvms/lvmd.yaml
• [x] Rebase on main

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.

In response to this:

TODO:

• [X] ~Generate Lister / Typed Clients due to otherwise mandatory import on lvm-operator introducing tons of dependencies~ replaced with a generic unstructured client
• [X] Resolve vendor conflict (see above) with normal resolution instead of vendor patch
• [ ] Create Cleanup Scenario that deletes old set of resources from installations that were present in 4.15/4.16
• [ ] Add upgrade test scenario to verify that LVMS works as expected
• [x] Add webhook yaml generation as part of the rebase script so that the validatingwebhook configuration is applied to LVMCluster normally
• [x] Use 4.17 Candidate instead of late 4.16 candidate once we have a CPaaS build out in the wild (need to trigger external replication that can be used during 4.17 testing cycle)
• [x] Add dynamic lvmd.yaml resolution via symlink into /var/lib/microshift/lvms/lvmd.yaml
• [x] Rebase on main

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.

In response to this:

TODO:

• [X] ~Generate Lister / Typed Clients due to otherwise mandatory import on lvm-operator introducing tons of dependencies~ replaced with a generic unstructured client
• [X] ~Resolve vendor conflict (see above) with normal resolution instead of vendor patch~ resolved by using dynamic client with discovery API for LVMCluster
• [ ] Create Cleanup Scenario that deletes old set of resources from installations that were present in 4.15/4.16
• [ ] Add upgrade test scenario to verify that LVMS works as expected
• [x] ~Add webhook yaml generation as part of the rebase script so that the validatingwebhook configuration is applied to LVMCluster normally~ added opinionated webhook generation with notes for further maintenance
• [x] ~Use 4.17 Candidate instead of late 4.16 candidate once we have a CPaaS build out in the wild (need to trigger external replication that can be used during 4.17 testing cycle)~ rebased on 4.17 candidate replicated to quay as aligned. Binaries / shas are equivalent and once release is happening we just need to retrigger the rebase script with the registry.redhat.io url before pushing out the candidate for Microshift. Since the images are the same this is however not endangering breaking anything.
• [x] Add dynamic lvmd.yaml resolution via symlink into /var/lib/microshift/lvms/lvmd.yaml
• [x] Rebase on main (seems I have to do this a lot)

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.

In response to this:

TODO:

• [X] ~Generate Lister / Typed Clients due to otherwise mandatory import on lvm-operator introducing tons of dependencies~ replaced with a generic unstructured client
• [X] ~Resolve vendor conflict (see above) with normal resolution instead of vendor patch~ resolved by using dynamic client with discovery API for LVMCluster
• [x] Create Cleanup Scenario that deletes old set of resources from installations that were present in 4.15/4.16
• [ ] Add upgrade test scenario to verify that LVMS works as expected
• [x] ~Add webhook yaml generation as part of the rebase script so that the validatingwebhook configuration is applied to LVMCluster normally~ added opinionated webhook generation with notes for further maintenance
• [x] ~Use 4.17 Candidate instead of late 4.16 candidate once we have a CPaaS build out in the wild (need to trigger external replication that can be used during 4.17 testing cycle)~ rebased on 4.17 candidate replicated to quay as aligned. Binaries / shas are equivalent and once release is happening we just need to retrigger the rebase script with the registry.redhat.io url before pushing out the candidate for Microshift. Since the images are the same this is however not endangering breaking anything.
• [x] Add dynamic lvmd.yaml resolution via symlink into /var/lib/microshift/lvms/lvmd.yaml
• [x] Rebase on main (seems I have to do this a lot)

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.

In response to this:

TODO:

• [X] ~Generate Lister / Typed Clients due to otherwise mandatory import on lvm-operator introducing tons of dependencies~ replaced with a generic unstructured client
• [X] ~Resolve vendor conflict (see above) with normal resolution instead of vendor patch~ resolved by using dynamic client with discovery API for LVMCluster
• [x] Create Cleanup Scenario that deletes old set of resources from installations that were present in 4.15/4.16
• [x] Add upgrade test scenario to verify that LVMS works as expected
• [x] ~Add webhook yaml generation as part of the rebase script so that the validatingwebhook configuration is applied to LVMCluster normally~ added opinionated webhook generation with notes for further maintenance
• [x] ~Use 4.17 Candidate instead of late 4.16 candidate once we have a CPaaS build out in the wild (need to trigger external replication that can be used during 4.17 testing cycle)~ rebased on 4.17 candidate replicated to quay as aligned. Binaries / shas are equivalent and once release is happening we just need to retrigger the rebase script with the registry.redhat.io url before pushing out the candidate for Microshift. Since the images are the same this is however not endangering breaking anything.
• [x] Add dynamic lvmd.yaml resolution via symlink into /var/lib/microshift/lvms/lvmd.yaml
• [x] Rebase on main (seems I have to do this a lot)

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.

• ~~OWNERS~~ [copejon]

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

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