diff --git a/rfcs/2020-04-04-2221-kubernetes-integration.md b/rfcs/2020-04-04-2221-kubernetes-integration.md
index f0cbcd237abcc..f7f191f5f7345 100644
--- a/rfcs/2020-04-04-2221-kubernetes-integration.md
+++ b/rfcs/2020-04-04-2221-kubernetes-integration.md
@@ -358,6 +358,9 @@ See [motivation](#motivation).
    [etc][container_runtimes]. Some even use [gVisor] or [Firecracker]. There
    might be differences in how different container runtimes handle logs.
 1. How do we want to approach Helm Chart Repository management.
+1. How do we implement liveness, readiness and startup probes?
+1. Can we populate file at `terminationMessagePath` with some meaningful
+   information when we exit or crash?
 
 ## Plan Of Attack
 
diff --git a/rfcs/2020-04-04-2221-kubernetes-integration/NOTES.md b/rfcs/2020-04-04-2221-kubernetes-integration/NOTES.md
new file mode 100644
index 0000000000000..1e80802f93bbf
--- /dev/null
+++ b/rfcs/2020-04-04-2221-kubernetes-integration/NOTES.md
@@ -0,0 +1,5 @@
+- We can pass thread limit to vector via env var, see
+  https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.18/#envvarsource-v1-core
+  via https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.18/#resourcefieldselector-v1-core
+
+- Optional extra env vars configmaps: https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.18/#configmapenvsource-v1-core