Stikked

halyard deployment

From Diminutive Kangaroo, 5 Years ago, written in Plain Text, viewed 464 times. This paste will perish in 1 Second.
URL https://paste.steamr.com/view/2f4f7263 Embed
Download Paste or View Raw
  1. PaaS enables developers to easily create applications without having to worry about setting up the underlying platform components. So if a developer wants a database, they just check a box, or make an API call, or use whatever mechanism that the PaaS provides to get one. They don’t have to install the database, they can just use it. OpenShift, Cloud Foundry, and Heroku are examples of a PaaS.
  2.  
  3.  
  4. spinnaker@halyard:/workdir$ kubectl get nodes
  5. NAME                                   STATUS   ROLES    AGE   VERSION
  6. 7b41da72-f250-4e49-9e11-f73bce94d29c   Ready    <none>   8d    v1.13.5
  7. 972210f9-cfbf-4cdc-b3a7-8231ec701685   Ready    <none>   8d    v1.13.5
  8. e6ccad96-fe41-446a-a847-251cced395c5   Ready    <none>   8d    v1.13.5
  9. spinnaker@halyard:/workdir$ ls
  10. spinnaker@halyard:/workdir$ hal deploy apply
  11. + Get current deployment
  12.   Success
  13. + Prep deployment
  14.   Success
  15. + Preparation complete... deploying Spinnaker
  16. + Get current deployment
  17.   Success
  18. + Apply deployment
  19.   Success
  20. + Run `hal deploy connect` to connect to Spinnaker.
  21. /home/spinnaker/.hal/default/install.sh must be executed with root permissions; exiting
  22. ! ERROR Error encountered running script. See above output for more
  23.   details.
  24. spinnaker@halyard:/workdir$ hal config provider kubernetes enable
  25. + Get current deployment
  26.   Success
  27. + Edit the kubernetes provider
  28.   Success
  29. Problems in default.provider.kubernetes:
  30. - WARNING Provider kubernetes is enabled, but no accounts have been
  31.   configured.
  32.  
  33. + Successfully enabled kubernetes
  34. spinnaker@halyard:/workdir$ CONTEXT=$(kubectl config current-context)
  35. spinnaker@halyard:/workdir$
  36. spinnaker@halyard:/workdir$ hal config provider kubernetes account add my-k8s-v2-account    --provider-version v2   --context $CONTEXT
  37. + Get current deployment
  38.   Success
  39. + Add the my-k8s-v2-account account
  40.   Success
  41. + Successfully added account my-k8s-v2-account for provider
  42.   kubernetes.
  43. spinnaker@halyard:/workdir$ hal config features edit --artifacts true
  44. + Get current deployment
  45.   Success
  46. + Get features
  47.   Success
  48. + Edit features
  49.   Success
  50. + Successfully updated features.
  51. spinnaker@halyard:/workdir$ hal config deploy edit --type distributed --account-name  my-k8s-v2-account
  52. + Get current deployment
  53.   Success
  54. + Get the deployment environment
  55.   Success
  56. + Edit the deployment environment
  57.   Success
  58. + Successfully updated your deployment environment.
  59. spinnaker@halyard:/workdir$ echo  minio123  | hal config storage s3 edit --endpoint  minio-service  --access-key-id minio  --secret-access-key
  60. + Get current deployment
  61.   Success
  62. + Get persistent store
  63.   Success
  64. - No changes supplied.
  65. spinnaker@halyard:/workdir$ hal config storage edit --type s3
  66. + Get current deployment
  67.   Success
  68. + Get persistent storage settings
  69.   Success
  70. - No changes supplied.
  71. spinnaker@halyard:/workdir$ hal deploy apply
  72. + Get current deployment
  73.   Success
  74. + Prep deployment
  75.   Success
  76. Problems in default.security:
  77. - WARNING Your UI or API domain does not have override base URLs
  78.   set even though your Spinnaker deployment is a Distributed deployment on a
  79.   remote cloud provider. As a result, you will need to open SSH tunnels against
  80.   that deployment to access Spinnaker.
  81. ? We recommend that you instead configure an authentication
  82.   mechanism (OAuth2, SAML2, or x509) to make it easier to access Spinnaker
  83.   securely, and then register the intended Domain and IP addresses that your
  84.   publicly facing services will be using.
  85.  
  86. + Preparation complete... deploying Spinnaker
  87. + Get current deployment
  88.   Success
  89. - Apply deployment
  90.   Generating all Spinnaker profile files and endpoints: Waiting on deployments to complete
  91. - Deploy spin-redis
  92.  
  93. - Deploy spin-clouddriver
  94.  
  95. - Deploy spin-front50
  96.  
  97. - Deploy spin-orca
  98.  
  99. - Deploy spin-deck
  100.  
  101. - Deploy spin-echo
  102.  
  103. - Deploy spin-gate
  104.  
  105. - Deploy spin-rosco
  106.  
  107.  

Reply to "halyard deployment"

Here you can reply to the paste above

Powered by Stikked