so i am running on a forked repo of the airbyte re...
# replication-troubleshooting
k
so i am running on a forked repo of the airbyte repo. If i want to upgrade, what else is required other then changing the image version tags in the
kustomization.yaml
file? do i need to port over
airbyte/kube/resources
to my own resource folder (
deployments/prd/us_east_2/resources
)? I have prod and staging deployment folders setup and deploying via flux.
s
The configs in
kube/resources
are base configs used in
kustomize build
, my understanding is that parameters in
.env
get patched into those configs so if you're using that config file, it's a good idea to bring the base configs over as well and make sure that
kustomization.yml
is pointing
bases
to their folder. You also need to bump the
AIRBYTE_VERSION
parameter in
.env
to match the docker image versions. Other than that I believe you should be good to go
🙏 1