Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

make partition and tenant this postgreslet is responsible configurable #23

Merged
merged 6 commits into from
Dec 16, 2020

Conversation

LimKianAn
Copy link
Contributor

  • Change the separator in a zalando postgresql name.
  • Unify the namespaces of our resources and zalando resources.
  • Add the flags partition-id and tenant.

- Change the separator in a zalando postgresql name.
- Unify the namespaces of our resources and zalando resources.
- Add the flags `partition-id` and `tenant`.
@LimKianAn LimKianAn requested review from majst01 and eberlep and removed request for majst01 December 10, 2020 20:14
@majst01 majst01 changed the title Prepare for deployment make partition and tenant this postgreslet is responsible configurable Dec 11, 2020
api/v1/postgres_types.go Outdated Show resolved Hide resolved
api/v1/postgres_types.go Show resolved Hide resolved
api/v1/postgres_types.go Outdated Show resolved Hide resolved
config/samples/database_v1_postgres.yaml Outdated Show resolved Hide resolved
pkg/pgletconf/pgletconf.go Outdated Show resolved Hide resolved
main.go Outdated Show resolved Hide resolved
@LimKianAn
Copy link
Contributor Author

@majst01 Changes are completed.

@LimKianAn
Copy link
Contributor Author

@eberlep If everything is alright, please merge it. Thanks!

return true
}

func (r *PostgresReconciler) createZalandoPostgresql(ctx context.Context, z *pg.ZalandoPostgres) (ctrl.Result, error) {
log := r.Log.WithValues("zalando postgresql", z.ToKey())

// todo: Create a ns if none.
// Make sure the namespace exists in the worker-cluster. // todo: Make sure it happens in the worker-cluster.
ns := z.Namespace
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I understand we use the same namespace for the Zanaldo PostgreSQL object as we use for the FI-TS Postgres object here?

If that's the case we might need to discuss this: The FI-TS object resides in our common "seed" cluster, whereas the Zalando object resides in the worker or service cluster. And if I remember correctly, we don't separate the FI-TS objects per tenant/project in the seed cluster, but might have to do so in the service cluster? If so, we cannot use the same namespace but have to separete them?

api/v1/postgres_types.go Show resolved Hide resolved
@eberlep eberlep merged commit 18de3a4 into main Dec 16, 2020
@majst01 majst01 deleted the prepare-for-deployment branch December 16, 2020 14:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants