# Hot reload for K8s objects

**URL:** <https://community.okteto.com/t/hot-reload-for-k8s-objects/381>\
**Category:** Help\
**Created:** [November 28, 2022, 5:36pm UTC](https://community.okteto.com/t/hot-reload-for-k8s-objects/381 "2022-11-28T17:36:22Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![scheung38](https://sea1.discourse-cdn.com/flex019/user_avatar/community.okteto.com/scheung38/32/205_2.png) [@scheung38](https://community.okteto.com/u/scheung38)\
**Post date:** [November 28, 2022, 5:36pm UTC](https://community.okteto.com/t/hot-reload-for-k8s-objects/381/1 "2022-11-28T17:36:22Z")

</div>

When we make a change for any k8s object, do we need to build --deploy ? Or k8s can also benefit from hot reload?

i.e changing ConfigMap or Secrets credentials in order to check authentication failure when connecting to MongoDB from Django we need to docker-compose -f production.yml build, push and kubectl apply -f manifest