Skip to main content

KERALA TOUR PACKAGE, DISCOVER KERALA.

DISCOVER KERALA
COCHIN-MUNNAR-THEKKADY-ALLEPPEY OR KUMARAKOM
(6 Nights / 7 Days)
(1 Night cochin- 2 Nights Munnar-1 Night Thekkady-2 Nights Alleppey or Kumarakom )


Day 1

Transfer from Cochin Airport./ Railway Station to Hotel
Cochin Sightseeing
Sunset Cruise
Overnight Stay at Cochin


Day 2
Breakfast
Departure for Munnar around 08:00 A.M
Arrival Munnar around 01:00 and transfer to hotel.
Afternoon free.
Dinner.
Overnight at Munnar.


Day 3

Breakfast
Munnar Sightseeing
Dinner.
Overnight at Munnar.


Day 4


Breakfast.
Departure for Thekkady around 08:00 A.M
Arrival Thekkady around 12:00 Noon & transfer to Hotel.
Visit Periyar Wild Life Sanctuary from 4:00 to 6:00P.M
Dinner.
Overnight at Thekkady.


Day 5


Breakfast
Departure for Alleppey or kumarakom around 08:00 A.M
Arrival Alleppey or Kumarakom around 1:00 P.M and transfer to Hotel.
Afternoon free at Alleppey or Kumarakom
Dinner.
Overnight at Alleppey or kumarakom.


Day 6


Breakfast
Day free for backwater cruise, between 10:00 A.M to 02:00 P.M
Afternoon free.
Dinner.
Overnight at Alleppey or Kumarakom.

Day 7

Breakfast
Departure for Cochin Airport/ Railway Station .


PACKAGE RATE
These rates are valid upto MAR 31Via AlleppeyPREMIUM PACKAGE
RATE (Rs)
34,660
ECONOMY PACKAGE
RATE (Rs)
17,965
BUDGET PACKAGE
RATE (Rs)11,423
Via KumarakomPREMIUM PACKAGE
RATE (Rs)
36,110

ECONOMY PACKAGE
RATE (Rs)
19,171

BUDGET PACKAGE
RATE (Rs)
11,843


VEHICLE RATE

Rate in (Rs).
Non/AC Indica
9,870
AC Indica
12,075
Non/AC Qualis
11,249
AC Qualis
13,454

Note: Total Package Rate = Appropriate Package Rate + Vehicle Rate.

The Rate will be Higher From 15 DEC to 20 JAN, than the above mentioned rates.
These rates are for One couple on Twin Sharing Basis.
For extra person additional charge will be applicable.
These Rates are “Net Payable Rate” by the Guest for 7 Day / 6 Night Package.

For Booking and Further Enquiry Contact,

Al Zarafa Tours & Travels Pvt, Ltd
1st Floor , Chammany Tower,
Kaloor, Cohin.
Ph: +91 0484-4047800/808, 2536030
Mob: 9446000800.

Comments

Post a Comment

Popular posts from this blog

Password reset too simplistic/systematic issue

Some time when we try to reset the password of our user in linux it will show as simple and systematic as below: BAD PASSWORD: it is too simplistic/systematic no matter how hard password you give it will show the same. Solution: ######### Check if your password is Ok with the below command, jino@ndz~$ echo 'D7y8HK#56r89lj&8*&^%&^%#56rlKJ!789l' | cracklib-check D7y8HK#56r89lj&8*&^%&^%#56rlKJ!789l: it is too simplistic/systematic Now Create a password with the below command : jino@ndz~$ echo $(tr -dc '[:graph:]' 7\xi%!W[y*S}g-H7W~gbEB4cv,9:E:K; You can see that this password will be ok with the cracklib-check. jino@ndz~$ echo '7\xi%!W[y*S}g-H7W~gbEB4cv,9:E:K;' | cracklib-check                 7\xi%!W[y*S}g-H7W~gbEB4cv,9:E:K;: OK Thats all, Thanks.
Post a Comment
Read more

Running K8s cluster service kubelet with Swap Memory Enabled

For enabling swap memory check the below link : https://jinojoseph.blogspot.com/2019/10/enable-swap-memory-using-swapfile-in.html # sudo vi /etc/systemd/system/kubelet.service.d/10-kubeadm.conf Add the KUBELET_EXTRA_ARGS line as below: ---------------------------------------- Environment="KUBELET_EXTRA_ARGS=--fail-swap-on=false" ExecStart= ExecStart=/usr/bin/kubelet $KUBELET_KUBECONFIG_ARGS $KUBELET_CONFIG_ARGS $KUBELET_KUBEADM_ARGS $KUBELET_EXTRA_ARGS Now kubelet.service changed on disk. Run 'systemctl daemon-reload' to reload units # sudo systemctl daemon-reload # sudo systemctl restart kubelet # sudo systemctl status kubelet That is all cheers :p
Post a Comment
Read more

Setting /etc/hosts entries during the initial deployment of an Application using k8s yaml file

Some times we have to enter specific hosts file entries to the container running inside the POD of a kubernetes deployment during the initial deployment stage itself. If these entries are not in place, the application env variables mentioned in the yaml file , as hostnames , will not resolve to the IP address and the application will not start properly. So to make sure the /etc/hosts file entries are already there after the spin up of the POD you can add the below entries in your yaml file. cat > api-deployment.yaml apiVersion: apps/v1 kind: Deployment metadata: spec:   template:     metadata:     spec:       volumes:       containers:       - image: registryserver.jinojoseph.com:5000/jinojosephimage:v1.13         lifecycle:           postStart:             exec:               command:...
Post a Comment
Read more