Skip to content
GitLab
Switch branch/tag
This project is mirrored from https://gitee.com/BiAn-MoShangHuaKai/velero.git. Pull mirroring failed .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
  1. 26 Mar, 2021 3 commits
  3. 25 Mar, 2021 4 commits
  5. 24 Mar, 2021 1 commit
  7. 17 Mar, 2021 1 commit
    • David L. Smith-Uchida's avatar
      Added volume snapshot test for backup/restore. (#3592) · e9c99783
      David L. Smith-Uchida authored 
      
Snapshot tests can be run with Ginkgo focus "Snapshot" and restic tests with Ginkgo focus "Restic".
Restic and volume snapshot tests can now be run simultaneously.
Added check for kibishii app start after restore.
Consolidated kibishii pod checks into waitForKibishiiPods.
Added WaitForPods function to e2e/tests/common.goSnapshot tests are skipped automatically on kind clusters.
Fixed issue where velero_utils InstallVeleroServer was looking for the Restic daemon set in the "velero" namespace only (was ignoring io.Namespace)
Signed-off-by: default avatarDave Smith-Uchida <dsmithuchida@vmware.com>
      e9c99783
  9. 16 Mar, 2021 3 commits
  11. 15 Mar, 2021 4 commits
  13. 11 Mar, 2021 3 commits
    • Ashish Amarnath's avatar
      Upgrade restic from v0.9.6 to v0.12.0 (#3528) · 2cddda84
      Ashish Amarnath authored 
      
* Upgrade restic from v0.9.6 to v0.12.0
Signed-off-by: default avatarAshish Amarnath <ashisham@vmware.com>

* add changelog
Signed-off-by: default avatarAshish Amarnath <ashisham@vmware.com>
      2cddda84
    • Bridget McErlean's avatar
      Use Credential from BSL for restic commands (#3489) · 9ffffda1
      Bridget McErlean authored 
      
* Use Credential from BSL for restic commands

This change introduces support for restic to make use of per-BSL
credentials. It makes use of the `credentials.FileStore` introduced in
PR #3442 to write the BSL credentials to disk. To support per-BSL
credentials for restic, the environment for the restic commands needs to
be modified for each provider to ensure that the credentials are
provided via the correct provider specific environment variables.
This change introduces a new function `restic.CmdEnv` to check the BSL
provider and create the correct mapping of environment variables for
each provider.

Previously, AWS and GCP could rely on the environment variables in the
Velero deployments to obtain the credentials file, but now these
environment variables need to be set with the path to the serialized
credentials file if a credential is set on the BSL.

For Azure, the credentials file in the environment was loaded and parsed
to set the environment variables for restic. Now, we check if the BSL
has a credential, and if it does, load and parse that file instead.

This change also introduces a few other small improvements. Now that we
are fetching the BSL to check for the `Credential` field, we can use the
BSL directly to get the `CACert` which means that we can remove the
`GetCACert` function. Also, now that we have a way to serialize secrets
to disk, we can use the `credentials.FileStore` to get a temp file for
the restic repo password and remove the `restic.TempCredentialsFile`
function.
Signed-off-by: default avatarBridget McErlean <bmcerlean@vmware.com>

* Add documentation for per-BSL credentials
Signed-off-by: default avatarBridget McErlean <bmcerlean@vmware.com>

* Address review feedback
Signed-off-by: default avatarBridget McErlean <bmcerlean@vmware.com>

* Address review comments
Signed-off-by: default avatarBridget McErlean <bmcerlean@vmware.com>
      9ffffda1
    • Bridget McErlean's avatar
      Partially revert adding credentials to VSL (#3561) · 3656f45f
      Bridget McErlean authored 
      
We are no longer adding the Credentials field to the VSL so this reverts
part the change that added it (#3409).

The original PR also added the `snapshot-location set` command. This
command only included options for setting the credential but is part of
the work for #2426. Due to this, the command has been left in place
(with the credentials option removed) but has been hidden.
Signed-off-by: default avatarBridget McErlean <bmcerlean@vmware.com>
      3656f45f
  15. 10 Mar, 2021 3 commits
  17. 09 Mar, 2021 3 commits
  19. 04 Mar, 2021 4 commits
  21. 01 Mar, 2021 2 commits
  23. 26 Feb, 2021 2 commits
  25. 24 Feb, 2021 2 commits
  27. 23 Feb, 2021 1 commit
  29. 22 Feb, 2021 2 commits
    • Bridget McErlean's avatar
      Use pod namespace from backup when matching PVBs (#3475) · 0246a32a
      Bridget McErlean authored 
      
* Use pod namespace from backup when matching PVBs

In #3051, we introduced an additional check to ensure that a PVB matched
a particular pod by checking both the name and the namespace of the pod.
This caused an issue when using a namespace mapping on restore. In the
case where a namespace mapping is being used, the check for whether a
PVB matches a particular pod will fail as the PVB was created for the
original pod namespace and is not aware of the new namespace mapping
being used. This resulted in PVRs not being created for pods that were
being restored into new namespaces. The restic init containers were
being created to wait on the volume restore, however this would cause
the restored pods to block indefinitely as they would be waiting for a
volume restore that was not scheduled.

To fix this, we use the original namespace of the pod from the backup to
match the PVB to the pod being restored, not the new namespace where
the pod is being restored into.

Fixes #3467.
Signed-off-by: default avatarBridget McErlean <bmcerlean@vmware.com>

* Explain why the namespace mapping can't be used
Signed-off-by: default avatarBridget McErlean <bmcerlean@vmware.com>
      0246a32a
    • Madhav Jivrajani's avatar
      added documentation for how velero handles encryption (#3463) · 046cb596
      Madhav Jivrajani authored 
      Signed-off-by: default avatarMadhav Jivrajani <madhav.jiv@gmail.com>
      046cb596
  31. 19 Feb, 2021 1 commit
    • David L. Smith-Uchida's avatar
      E2E tests now run in multiple clouds in addition to KIND (#3286) · 45d53178
      David L. Smith-Uchida authored 
      
Split plug-in provider into cloud provider/object provider
Moved velero install/uninstall for tests into velero_utils
Added remove of CRDs to test v elero uninstall
Added remove of cluster role binding to test velero uninstall
Added dump of velero describe and logs on error
Added velero namespace argument to velero_utils functions
Modified api group versions e2e tests to use VeleroInstall
Added velero logs dumps for api group versions e2e testing
Added DeleteNamespace to test/e2e/common.go
Fixed VeleroInstall to use the image specified
Changed enable_api_group_versions_test to use veleroNamespace instead of hardcoded "velero"
Signed-off-by: default avatarDave Smith-Uchida <dsmithuchida@vmware.com>
      45d53178
  33. 18 Feb, 2021 1 commit

免费DevSecOps平台，让您的项目体验完整的DevSecOps流程，让项目更安全