chore(examples): add nextcloud

[SmsS4]

Hello i wrote an example for nextcloud + grafana using cdk8s in typescript.
This example includes:

• nextcloud
• mariadb
• redis
• traefik
• cert-manager
• certificate issuer
• victoria metrics
• grafana
  and these components of cdk8s and cdk8s+
• Helm
• Secret
• Deployment
• Container
• EnvValue
• Service
• Ingress
• PVC
• ApiObject and JsonPatch
• ConfigMap
• InitContainer

I had to read lots of cdk8s's document and other examples to write this, so i think this example is not that bad :))

[SmsS4]

I thinks it's fixed now
Could you please trigger build action? @iliapolo
Thanks.

[vinayak-kukreja]

Hey @SmsS4 , apologies for the delay. Would you still like to work on this PR?

[SmsS4]

No problem
Yes I still like to work on this PR
Thanks for reply

[vinayak-kukreja]

Great, I will review the PR this week(asap). Thank you for opening a PR with us.

[vinayak-kukreja]

Hey, this is great!! :)

I just have a few NITs, let me know if you have any queries related to them.

[vinayak-kukreja]

Hey @SmsS4, thank you for contributing. Changes LGTM.

I see build fails because some files are being changed with the new merge,

Error: Files were changed during build (see build log). If this was triggered from a fork, you will need to update your branch.

I believe integrating these changes on your branch and running the workflow would succeed. Let me know once you do that and I can approve it again. :)

[SmsS4]

I think this should fix build problem @vinayak-kukreja

[SmsS4]

I'm 99% sure build won't fail anymore :)

[SmsS4]

I'm 99% sure build won't fail anymore :)

I didn't see merge conflict :) I will resolve it tomorrow or later today

[SmsS4]

@vinayak-kukreja I think everything is OK now

[SmsS4]

Looks like build failed because of network issue
and conflict was for yaml libary version

[iliapolo]

@SmsS4 Hi!

Apologies for the long back and forth here, but after some further internal discussion I'm afraid we cannot accept this PR as it currently stands. This examples repository is focused on showcasing cdk8s patterns and features, not specific tools or products.

Here is my suggestion for going forward.

• Some parts of this PR can be generally helpful, for example your usage of PVC and JsonPatch. If you are willing, please scope this PR down to focus on specific features, and create a small dedicated examples for each of those.
• For the parts of the code that create specific products (e.g mariadb, next cloud) I suggest you self publish those constructs similar to cdk8s-grafana. These packages will then appear on ConstructHub and have visibility for the larger CDK eco system.

Thanks!

Reconsidered

[SmsS4]

Thanks for response :)
OK I will add smaller examples