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.

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

Bug 2144527 #281

Closed
wants to merge 85 commits into from
Closed

Bug 2144527 #281

wants to merge 85 commits into from

Conversation

yati1998
Copy link
Contributor

Avoid extra RPC calls as request will be requested again for
updating the LastSyncTime in the status. The image need to be
promoted only one time not always during the reconcile.

backport of #280

nixpanic and others added 30 commits May 6, 2022 16:13
When kubernetes-csi-addons are included in the ODF product, we need to
document the review/backport guidelines and list the maintainers. This
repository is currently part of the responsibilities of the Ceph-CSI
team.

Signed-off-by: Niels de Vos <[email protected]>
(cherry picked from commit 6b32ad6)
Dependabot does not need to report available updates for vendored
dependencies in the downstream repository. Updates to dependencies are
synced from the upstream repository when needed. There is also the
"Upstream First" requirement, which we follow closely.

See-also: https://docs.github.com/en/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates#open-pull-requests-limit
Signed-off-by: Niels de Vos <[email protected]>
(cherry picked from commit 6e4f4ba)
As ODF-Operator is used for deploying the CSI-Addons components, the
CSI-Addons operator does not need to be visible in the OperatorHub.

Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=2042997
Signed-off-by: Niels de Vos <[email protected]>
(cherry picked from commit 15e9b1a)
There is no upstream icon for the CSI-Addons project yet. All operators
are required to have an icon before they can be published. Until there
is an icon in upstream, use the standard Red Hat icon for product
builds.

Signed-off-by: Niels de Vos <[email protected]>
Sync upstream main branch to downstream
This commits add instructions to resolve conflicts if they
arise while syncing upstream changes.

Signed-off-by: Rakshith R <[email protected]>
[DOWNSTREAM-ONLY]: document process for resolving conflicts
Sync rhs:main with csi-addons:main NetworkFence: Explicitly mentioned Fenced and Unfenced state
sync the upstream main branch
Dependabot can update GitHub Actions in the workflows. It is useful to
have them updated regularly so that enhancements and bugfixes get
included.

Signed-off-by: Niels de Vos <[email protected]>
This commit enables the multigroup api to allow
different group for csi-addons and volume-replication

updates: csi-addons#116

Signed-off-by: yati1998 <[email protected]>
This commit adds types.go file for volumereplication
and volumereplicationclass that can be used to create the
respective crds.
This is a part of movement of volume replication operator
to kubernetes-csi-addons
https://github.com/csi-addons/volume-replication-operator/tree/main/api/v1alpha1

updates: csi-addons#116

Signed-off-by: yati1998 <[email protected]>
This commit generates the volumereplication
and volumereplicationclass crds using the
make manifest and updates the deepcopy using
make generate.
The genrated files are stored in api/v1aplha1/
This is the part of moving volume replication operator
to kubernetes-csi-addons repo.
https://github.com/csi-addons/volume-replication-operator

Updates: csi-addons#116

Signed-off-by: yati1998 <[email protected]>
This commit adds rbac rule for volume replication in csi-addons
These rules have been added from
https://github.com/csi-addons/volume-replication-operator/tree/main/config/rbac

Signed-off-by: yati1998 <[email protected]>
This commit modifies the project structure to support
the multi group.
The changes include:
1. moving api/v1alpha to apis/csiaddons/v1alpha/
2. creating controllers/csiaddons/
Once we add controller logic for volume replication
we can create another group inside controller/.

Signed-off-by: yati1998 <[email protected]>
This commit adds Documentation for the volume
replication and volume replication class CRs.
This has been added from Volume Replication
operator Readme:
https://github.com/csi-addons/volume-replication-operator/blob/main/README.md

Signed-off-by: yati1998 <[email protected]>
Madhu-1 and others added 29 commits August 30, 2022 15:45
golang need to be updated to 1.18 in Dockerfile

Signed-off-by: Madhu Rajanna <[email protected]>
Yug left the company, so removing him from the team.

Signed-off-by: Niels de Vos <[email protected]>
…ry-pick-53-to-release-4.12

[release-4.12] sync downstream with upstream
…ry-pick-55-to-release-4.12

[release-4.12] [DOWNSTREAM-ONLY] remove Yug from OWNERS
Kubernetes 1.25 requires Go 1.19 or newer. In order to update the
vendored dependencies, we'll need to use it too.

Signed-off-by: Niels de Vos <[email protected]>
This commit adds lastsynctime to volume
replicationstatus and updates the crds.

Signed-off-by: yati1998 <[email protected]>
This commit creates internal grpc to get volume
replication information.

Signed-off-by: yati1998 <[email protected]>
this commit updates the vendor to get latest
spec.

Signed-off-by: yati1998 <[email protected]>
This commit adds reconcile logic to update the
last sync time.

Signed-off-by: yati1998 <[email protected]>
…ry-pick-59-to-release-4.12

[release-4.12] Sync the upstream changes from `csi-addons/kubernetes-csi-addons:main` into the `main` branch
resolveEndpoint get the pod object to resolve
the ip address as the pod object is deleted
resolveEndpoint will fail to get the pod and
it blocks the csiaddonsnodes object from getting
deleted because of this logs will get flooded
and other csiaddons operation might also fail.

To fix this problem call resolveEndpoint only
if the csiaddonsnodes object is not deleted.

Signed-off-by: Madhu Rajanna <[email protected]>
(cherry picked from commit 08d7a49)
BUG 2132892: controller: fix csiaddonsnodes object deletion
LastSyncTime can be optional and nil also, there
is no strict check for it and if we dont have this
check the default UNIX time will get added to the
CR which doesnt make sense. If the time is not
present keeping the last known LastSyncTime itself.

Signed-off-by: Madhu Rajanna <[email protected]>
(cherry picked from commit 233112e)
csi-addons/spec#47
has the defined errors for the
GetVolumeReplicationInfo RPC call.

Signed-off-by: Madhu Rajanna <[email protected]>
(cherry picked from commit 09674b2)
Added known error for GetVolumeReplicationInfo
RPC call as per the predefined error messages
in the csiaddons spec.

Signed-off-by: Madhu Rajanna <[email protected]>
(cherry picked from commit 5c0550d)
Bug 2136457: replication: update LastSyncTime if its not nil
Reduce the schedule time by half to get the
latest update and also to avoid the
inconsistency between the last sync time in
the VR and the Storage system.

The user can see updates for RPO that are not
stuck in a bad schedule race i.e VR checks
and finds sync time as t-5m and just after
that storage system updates it to t+x.
If we checked every 1/2 of schedule we will
update it to t+x in t+s/2

Signed-off-by: Madhu Rajanna <[email protected]>
(cherry picked from commit 8b40a09)
BUG 2140697: replication: reduce the reqeue time for GetReplicationInfo
Avoid extra RPC calls as request will be requested again for
updating the LastSyncTime in the status. The image need to be
promoted only one time not always during the reconcile.

fixes: csi-addons#250

Co-authored-by: Madhu Rajanna <[email protected]>
Signed-off-by: yati1998 <[email protected]>
@yati1998 yati1998 closed this Dec 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants