Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
K
KubernetesClusterSetup
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Deploy
Releases
Package registry
Model registry
Operate
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Helmut Hutzler
KubernetesClusterSetup
Commits
82e8558b
Commit
82e8558b
authored
4 years ago
by
Helmut Hutzler
Browse files
Options
Downloads
Patches
Plain Diff
Modified build-staging.sh
parent
ca362df1
No related branches found
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
GIT-Deployment/build-scripts/GENERIC/build-staging.sh
+19
-10
19 additions, 10 deletions
GIT-Deployment/build-scripts/GENERIC/build-staging.sh
with
19 additions
and
10 deletions
GIT-Deployment/build-scripts/GENERIC/build-staging.sh
+
19
−
10
View file @
82e8558b
...
...
@@ -15,15 +15,24 @@
# CI_PROJECT_ID must be copied from your GITLAB project
# CI_REGISTRY_NAME must match your harbor configuration
# KUBE_NAMESPACE is set to the namespace created by GITLAB accessing the Kubernetes cluster a first time
# INGRESS_HOST is set to the external name where the app will be reachable
# Note : Double check the hostname isn't arlready used by a different ingress ( In that case the service will show status pendind )
# Currentlly following hostnames are configured via DNS for our test cluster
# Hostname Port
# ============== ====
# kube-master-h1 9601
# kube-master-h2 9602
# kube-master-h3 9603
# kube-master-h4 9604
#
# In any case we expect that you have create images like
# In any case we expect that you have create images like
with naming syntay <CI_PROJECT_NAME>-<CI_ENVIRONMENT_NAME> like:
# - harbor.informatik.fh-nuernberg.de/hutzler/kaniko-demo-staging
#
CI_PROJECT_NAME
=
kaniko-demo
CI_PROJECT_ID
=
3
556
CI_PROJECT_NAME
=
oidc-autologin
CI_PROJECT_ID
=
3
245
CI_ENVIRONMENT_NAME
=
staging
SERVICE_PORT
=
960
3
INGRESS_HOST
=
"kube-master-h
3
.informatik.fh-nuernberg.de"
SERVICE_PORT
=
960
4
INGRESS_HOST
=
"kube-master-h
4
.informatik.fh-nuernberg.de"
CI_REGISTRY_NAME
=
"harbor.informatik.fh-nuernberg.de/hutzler"
# You don't need to change these values are derived form above paramters
...
...
@@ -31,7 +40,7 @@ export KUBE_NAMESPACE=$CI_PROJECT_NAME"-"$CI_PROJECT_ID"-"$CI_ENVIRONMENT_NAME
export
SERVICE_ACCOUNT
=
${
KUBE_NAMESPACE
}
-service-account
echo
"KUBE_NAMESPACE : "
$KUBE_NAMESPACE
echo
"SERVICE-ACCOUNT: "
$SERVICE_ACCOUNT
#
echo
"INGRESS_HOST: "
$INGRESS_HOST
#
CI_REGISTRY_IMAGE
=
$CI_REGISTRY_NAME
"/"
$CI_PROJECT_NAME
"-"
$CI_ENVIRONMENT_NAME
POD_PORT
=
80
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment