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 knative default #3403

Merged
merged 12 commits into from Apr 2, 2019
Merged

Conversation

abbi-gaurav
Copy link
Member

@abbi-gaurav abbi-gaurav commented Mar 28, 2019

Description

  • get upgrade working
  • verify eventing flow with upgrade
  • remove all feature flags
  • remove or clean up any hardcodings
  • ensure install works on minikube
  • ensure install works on cluster
  • ensure clean upgrade works
  • Replace PR images with develop images

Related issue(s)
See also #3017

@abbi-gaurav abbi-gaurav self-assigned this Mar 28, 2019
@abbi-gaurav abbi-gaurav added the area/eventing Issues or PRs related to eventing label Mar 28, 2019
@abbi-gaurav
Copy link
Member Author

/test pre-master-kyma-integration

@abbi-gaurav
Copy link
Member Author

/test pre-master-kyma-gke-upgrade

Copy link
Contributor

@mszostok mszostok left a comment

Choose a reason for hiding this comment

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

LGTM from the ServicCatalog perspective

You removed

 -memory 10240 -disk_size 30g

and right now Kyma will have enabled knative by default. What about the memory and disk size? our installation will not need higher resource definition?

Should you consider to add flag for disabling knative? Installing it for local development sometimes could be not needed (plus I do not want to allocate higher memory and disk size if I'm not using such functionality)

@abbi-gaurav
Copy link
Member Author

/test pre-master-kyma-integration

@abbi-gaurav
Copy link
Member Author

LGTM from the ServicCatalog perspective

You removed

 -memory 10240 -disk_size 30g

and right now Kyma will have enabled knative by default. What about the memory and disk size? our installation will not need higher resource definition?

Should you consider to add flag for disabling knative? Installing it for local development sometimes could be not needed (plus I do not want to allocate higher memory and disk size if I'm not using such functionality)

@mszostok, going further, kyma eventing will only be built on top of knative eventing. So we do not have the option to optionally enable or disable knative. I removed this after verifying that the current resource allocation was working fine. The reason for 10g memory is unknown to me as Knative minikube installlation also uses 8g

if ($SKIP_MINIKUBE_START -eq $false) {
Invoke-Expression -Command "${SCRIPTS_DIR}\minikube.ps1 -vm_driver ${VM_DRIVER} -domain ${DOMAIN} ${MINIKUBE_EXTRA_ARGS}"
Invoke-Expression -Command "${SCRIPTS_DIR}\minikube.ps1 -vm_driver ${VM_DRIVER} -domain ${DOMAIN}
Copy link

Choose a reason for hiding this comment

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

Missing " at the end

Copy link
Member Author

Choose a reason for hiding this comment

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

I will create a second PR for this. To unblock other tasks, I will merge it once the tests succeed.

ghost
ghost previously requested changes Apr 2, 2019
Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

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

See comments

@abbi-gaurav abbi-gaurav dismissed ghost ’s stale review April 2, 2019 14:58

as discussed, it will be added in next pr

@abbi-gaurav abbi-gaurav merged commit 7fcd754 into kyma-project:master Apr 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/eventing Issues or PRs related to eventing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants