-
Notifications
You must be signed in to change notification settings - Fork 8
/
Copy pathhop.yaml
196 lines (169 loc) · 7.68 KB
/
hop.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
blocks:
- name: hop-web-ingress
content:
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: hop-web-ingress
namespace: hop
annotations:
cert-manager.io/cluster-issuer: cluster-issuer
kubernetes.io/tls-acme: "true"
spec:
ingressClassName: public
tls:
- hosts:
- "{{ $cndi.get_arg(hostname) }}"
secretName: cluster-issuer-private-key
rules:
- host: "{{ $cndi.get_arg(hostname) }}"
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: hop-web
port:
name: http
prompts:
- $cndi.get_block(https://raw.githubusercontent.com/polyseam/cndi/main/blocks/common/cluster/core-prompts.yaml):
{}
- $cndi.get_block(https://raw.githubusercontent.com/polyseam/cndi/main/blocks/{{ $cndi.get_prompt_response(deployment_target_provider) }}/core-prompts.yaml):
{}
- name: deploy_hop_ingress
default: true
message: >-
Do you want to expose Hop to the web?
type: Confirm
- name: hop_hostname
message: "Please enter the domain name you want hop to be accessible on:"
default: hop.example.com
type: Input
validators:
- hostname # FQDN
condition:
- "{{ $cndi.get_prompt_response(deploy_hop_ingress) }}"
- ==
- true
- name: hop_server_password
message: Please enter the hop server password you want to use for hop
default: admin
type: Secret
outputs:
cndi_config:
cndi_version: v2
project_name: "{{ $cndi.get_prompt_response(project_name) }}"
provider: "{{ $cndi.get_prompt_response(deployment_target_provider) }}"
distribution: "{{ $cndi.get_prompt_response(deployment_target_distribution) }}"
infrastructure:
cndi:
$cndi.get_block(https://raw.githubusercontent.com/polyseam/cndi/main/blocks/common/cluster/observability-config.yaml):
condition:
- "{{ $cndi.get_prompt_response(deploy_grafana_ingress) }}"
- ==
- true
$cndi.get_block(https://raw.githubusercontent.com/polyseam/cndi/main/blocks/common/cluster/argocd-config.yaml):
condition:
- "{{ $cndi.get_prompt_response(deploy_argocd_ingress) }}"
- ==
- true
cert_manager:
email: "{{ $cndi.get_prompt_response(cert_manager_email) }}"
external_dns:
$cndi.get_block(https://raw.githubusercontent.com/polyseam/cndi/main/blocks/external-dns/config/{{ $cndi.get_prompt_response(dns_provider) }}.yaml):
condition:
- "{{ $cndi.get_prompt_response(enable_external_dns) }}"
- ==
- true
nodes:
$cndi.get_block(https://raw.githubusercontent.com/polyseam/cndi/main/blocks/{{ $cndi.get_prompt_response(deployment_target_provider) }}/basic-node-pool.yaml):
{}
cluster_manifests:
hop-server-secret:
apiVersion: v1
kind: Secret
metadata:
name: hop-server
namespace: hop
type: Opaque
stringData:
pass: $cndi_on_ow.seal_secret_from_env_var(HOP_SERVER_PASSWORD)
hop-server-pvc:
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: hop-server-pvc
namespace: hop
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 1Gi
hop-web-ingress:
$cndi.get_block(hop-web-ingress):
args:
ingress_name: hop-web-ingress
hostname: "{{ $cndi.get_prompt_response(hop_hostname) }}"
condition:
- "{{ $cndi.get_prompt_response(deploy_hop_ingress) }}"
- ==
- true
external-dns-secret:
$cndi.get_block(https://raw.githubusercontent.com/polyseam/cndi/main/blocks/external-dns/secret/{{ $cndi.get_prompt_response(dns_provider) }}.yaml):
condition:
- "{{ $cndi.get_prompt_response(enable_external_dns) }}"
- ==
- true
hop-ns:
apiVersion: v1
kind: Namespace
metadata:
name: hop
applications:
hop:
targetRevision: HEAD
destinationNamespace: hop
repoURL: "https://github.com/apache/hop.git"
path: helm/hop
values:
server:
persistence:
enabled: true
existingClaim: hop-server-pvc
env:
$cndi.get_block(https://raw.githubusercontent.com/polyseam/cndi/main/blocks/common/git-credentials-{{ $cndi.get_prompt_response(git_credentials_mode) }}-env.yaml):
{}
$cndi.get_block(https://raw.githubusercontent.com/polyseam/cndi/main/blocks/{{ $cndi.get_prompt_response(deployment_target_provider) }}/env.yaml):
{}
$cndi.get_block(https://raw.githubusercontent.com/polyseam/cndi/main/blocks/common/cluster/env.yaml):
{}
$cndi.comment(hop-heading): Hop Connection Parameters
HOP_SERVER_PASSWORD: "{{ $cndi.get_prompt_response(hop_server_password) }}"
readme:
project_name: "# {{ $cndi.get_prompt_response(project_name) }}"
$cndi.get_string(https://raw.githubusercontent.com/polyseam/cndi/main/blocks/common/cluster/core-readme.md):
{}
$cndi.get_string(https://raw.githubusercontent.com/polyseam/cndi/main/blocks/{{ $cndi.get_prompt_response(deployment_target_provider) }}/core.md):
{}
$cndi.get_string(https://raw.githubusercontent.com/polyseam/cndi/main/blocks/{{ $cndi.get_prompt_response(deployment_target_provider) }}/{{ $cndi.get_prompt_response(deployment_target_distribution) }}.md):
{}
hop: |
# Apache Hop Deployment Guide
This Template deploys a Standalone production ready [Apache Hop](https://hop.apache.org) application on a Kubernetes cluster using Helm.
Apache Hop (Hop Orchestration Platform) is an open-source data integration platform designed to facilitate efficient and flexible data transformation and orchestration.
With its lightweight, extensible architecture, Apache Hop supports a wide range of data sources and destinations, making it ideal for complex data pipelines and ETL processes.
## Customizing Your Deployment
Tailor your Apache Hop deployment to your specific needs by adjusting the values in the `values.yaml` file. Important configuration options include:
- **Persistence:** Activate and configure persistent storage options for Apache Hop projects and workflows.
- **Database:** Set up external database connections for storing metadata or handling transformation data more effectively.
- **Resources:** Define CPU and memory limits and requests to optimize the performance of Apache Hop pods.
- **Ingress:** Adjust Ingress configurations to facilitate external access to the Apache Hop Web interface.
For a comprehensive list of all configuration options, refer to the Helm chart's documentation or the [values.yaml](https://github.com/apache/hop/blob/master/helm/hop/values.yaml) file within the chart repository.
## Verifying Apache Hop
Once Apache Hop is deployed and access is configured (via port forwarding, Ingress, or ExternalDNS), it's important to verify that the platform is accessible:
**Access the Web Interface**:
- Open a web browser and navigate to the domain set up for Apache Hop, e.g., `https://hop.yourdomain.com`.
- The Apache Hop browser application should appear, indicating successful deployment and accessibility.
Ensure to adapt the steps and URLs mentioned to fit the specific setup and configuration of your Apache Hop environment.