first :Shipper is down (spec.replicas: 0) before applying objects
then: shipperctl backup restore -v -f xxx.yaml failed
root@test-108:/opt/addons/shipper#
root@test-108:/opt/addons/shipper# kubectl get all -n shipper-system
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/shipper-validating-webhook ClusterIP 10.1.216.107 <none> 443/TCP 29h
NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/shipper 0/0 0 0 29h
NAME DESIRED CURRENT READY AGE
replicaset.apps/shipper-5df5c5fbc6 0 0 0 29h
root@test-108:/opt/addons/shipper# shipperctl backup restore -v -f bkup-mgm-04-09.yaml
Making sure shipper is down... done
Making sure there are no Shipper objects lying around... done
Would you like to see an overview of your backup? [y/n]: y
NAMESPACE RELEASE NAME OWNING APPLICATION
test super-server-bd708e4b-0 super-server
Would you like to review backup? [y/n]: y
- application:
apiVersion: shipper.booking.com/v1alpha1
kind: Application
metadata:
annotations:
kubectl.kubernetes.io/last-applied-configuration: |
......
Would you like to restore backup? [y/n]: y
Error! failed to apply application: Internal error occurred: failed calling webhook "shipper.booking.com": Post https://shipper-validating-webhook.shipper-system.svc:443/validate?timeout=30s: dial tcp 10.1.216.107:443: connect: connection refused
first :Shipper is down (spec.replicas: 0) before applying objects then: shipperctl backup restore -v -f xxx.yaml failed